mythfilldatabase crashed with SIGILL in MythContext::ClearSettingsCache()

Bug #331816 reported by Gregor Rosenauer
6
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: mythtv

crash report via apport. Got a crash from mythfilldatabase on an automatic run, using tv_grab_ch_search
Possibly cause by the fact that Mythtv won't connect the channels found by an automatic scan with the channels found by tv_grab_ch_seach although the channel short names do match, so it should be possible to do automatically...
As I have not yet manually connected / merged the channels, maybe this results in a crash in mythfilldatabase as no channels are found...?
Using Ubuntu jaunty (development branch) 9.04, latest dist-upgrade 18/02/2009

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/mythfilldatabase
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.21.0+fixes19961-0ubuntu2
ProcCmdline: /usr/bin/mythfilldatabase
ProcEnviron: PATH=(custom, no user)
Signal: 4
SourcePackage: mythtv
StacktraceTop:
 ?? ()
 MythContext::ClearSettingsCache ()
 MythContext::readyRead () from /usr/lib/libmyth-0.21.so.0
 readyReadThread_iffound () from /usr/lib/libmyth-0.21.so.0
 MythSocket::readyReadThread ()
Title: mythfilldatabase crashed with SIGILL in MythContext::ClearSettingsCache()
Uname: Linux 2.6.28-8-generic i686
UserGroups: audio cdrom dialout video

Revision history for this message
Gregor Rosenauer (grexe) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
MythContext::ClearSettingsCache (this=0x8bb3650, myKey=
MythContext::readyRead (this=0x8bb3650, sock=0x8bde550)
readyReadThread_iffound (sock=0x8bde550)
MythSocket::readyReadThread () at mythsocket.cpp:908

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
visibility: private → public
Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to improve Mythbuntu. The mythtv developers upstream have stopped focusing on 0.21 based reports in preparation for a 0.22 release later this year. Is this issue reproducible on 0.22? If it is, we can try to forward this bug upstream with a stacktrace/backtrace 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!

Changed in mythtv (Ubuntu):
status: New → Incomplete
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.