Ubuntu
mythtv package

mythcommflag crashed with SIGSEGV

Bug #190787 reported by MarkJBobak
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MythTV
Invalid
Unknown
mythtv (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: mythtv

I'm running Hardy Heron, and according to update-manager, I'm fully up-to-date.

This crash just happened, and since it's mythcommflag that runs in the background, I'm not sure if it happens immediately on execution.....

ProblemType: Crash
Architecture: amd64
Date: Sun Feb 10 16:02:37 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/mythcommflag
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.20.99+trunk15849-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/bin/mythcommflag -j 181 -V 3
ProcCwd: /
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: mythcommflag crashed with SIGSEGV
Uname: Linux mythbox 2.6.24-7-generic #1 SMP Thu Feb 7 00:56:31 UTC 2008 x86_64 GNU/Linux
UserGroups: audio cdrom dialout video
SegvAnalysis:
 Segfault happened at: 0x415798: movzbl (%rax,%r14,1),%eax
 PC (0x00415798) ok
 source "(%rax,%r14,1)" (0x02981734) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA

See original description
Tags: apport-crash
Revision history for this message
MarkJBobak (mark-bobak) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:ClassicSceneChangeDetector::processFrame (this=0x869260,
ClassicCommDetector::ProcessFrame (this=0x81a1c0,
ClassicCommDetector::go (this=0x81a1c0) at ClassicCommDetector.cpp:441
DoFlagCommercials (showPercentage=<value optimized out>,
FlagCommercials (chanid=@0x7fff9bc444c0, starttime=<value optimized out>)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in mythtv:
importance: Undecided → Medium
Bug Watch Updater (bug-watch-updater)
Changed in mythtv:
status: Unknown → New
David Morris (dave-greenacre)
Changed in mythtv:
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in mythtv:
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in mythtv:
status: Confirmed → New
Kees Cook (kees)
description: updated
Bug Watch Updater (bug-watch-updater)
Changed in mythtv:
status: New → Invalid
Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to improve Mythbuntu by reporting this issue. I am closing this ticket for a combination of reasons:

1. This ticket is quite old and the mythtv developers upstream have stopped focusing on 0.21 based reports
2. This issue would need to be reproduced on 0.22 with a new stack trace

If you can reproduce this on 0.22, please attach traces to a new ticket and we can try to forward this bug upstream to get the right eyes focused on it.

We have builds of mythtv 0.22 available on a PPA to test. Please follow the directions at http://mythbuntu.org/auto-builds to enable them.

WARNING: If you intend to revert back to 0.21 after testing, you will need to back up your database before upgrading.

    Thanks again!

Changed in mythtv (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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