mythbackend crashed with SIGSEGV in __libc_start_main()

Bug #958674 reported by odror
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)
New
Undecided
Unassigned

Bug Description

it started when I typed

mythtv-setup

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-backend 2:0.25.0~master.20120316.53761e2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 18 10:01:47 2012
ExecutablePath: /usr/bin/mythbackend
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythbackend --syslog local7 --user mythtv
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4e7fde: mov (%rdi),%rax
 PC (0x004e7fde) ok
 source "(%rdi)" (0x62006f004a0020) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x422dd0, argc=5, ubp_av=0x7fff7d147c18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff7d147c08) at libc-start.c:226
Title: mythbackend crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: audio cdrom dialout video

Revision history for this message
odror (ozdror) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #949291, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.