After some testing it looks like deleting a recording doesn't have anything to do with this. Exiting a playback of a recording and then pressing escape to exit back to the menu is enough to cause a segfault.
This time i got a better backtrace from the core dump. Torbjörn Jansson <mailto:[EMAIL PROTECTED]> wrote: > I've managed to get mythfrontend to segfault a few times, it > only happens when i delete a recording from the watch > recording screen and before the recording is completely > deleted i press escape to get back to the menu. > > I deleted a file and then quickly pressed esc. > > The back trace i got from the crash (core dump file) may not > be of much use, it is unusually short, maybe the stack got corrupted > or something. > > ----- > #0 0x05884ea2 in QObject::disconnectInternal () from > /usr/lib/qt-3.3/lib/libqt-mt.so.3 > (gdb) thread apply all bt full > > Thread 4 (process 5128): > #0 0x00000206 in ?? () > No symbol table info available. > Cannot access memory at address 0x0 > #0 0x05884ea2 in QObject::disconnectInternal () from > /usr/lib/qt-3.3/lib/libqt-mt.so.3 > (gdb) > ---- > > Any ideas? Maybe someone else have also seen this?
segfault.txt.bz2
Description: Binary data
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
