mythcommflag crashed with SIGSEGV

Bug #1017009 reported by rmb
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Undecided
Unassigned

Bug Description

back end crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-backend 2:0.25.0+fixes.20120622.73bc45e-0ubuntu0mythbuntu4 [origin: LP-PPA-mythbuntu-0.25]
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
Uname: Linux 3.2.0-25-generic-pae i686
NonfreeKernelModules: nvidia
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythtranscode.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
CrashCounter: 1
CrashDB: mythbuntu
Date: Sat Jun 23 20:42:22 2012
ExecutablePath: /usr/bin/mythcommflag
InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythcommflag -j 108 --noprogress --verbose general --loglevel info --syslog local7
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb58b4038: cmp 0xc(%eax),%edi
 PC (0xb58b4038) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/nvidia-current/tls/libnvidia-tls.so.295.40
Title: mythcommflag crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: audio cdrom dialout video

Revision history for this message
rmb (rmball28) wrote :
Revision history for this message
Thomas Mashos (tgm4883) wrote :

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.

Changed in mythbuntu:
status: New → Expired
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.