[mythtv] Core dump in CVS

[Brian Foddy]

Been playing a bit more.  It hasn't yet died playing a recorded
show, all on live TV.  5 dumps so far since rebuilding with -g,
no 2 similar stack traces yet, but most several levels down
inside libqt-mt.so.3.  The latest clean core:

#0  0x40a5d42d in malloc () from /lib/i686/libc.so.6
#1  0x40a5d262 in malloc () from /lib/i686/libc.so.6
#2  0x4099a7fe in operator new(unsigned) () from /usr/lib/libstdc++.so.5
#3  0x40680a43 in QGList::insertAt(unsigned, void*) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#4  0x40305cec in QSessionManager::requestPhase2() () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#5  0x402fb653 in QApplication::processNextEvent(bool) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#6  0x402fcfb8 in QApplication::processEvents(int) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#7  0x40364d57 in QApplication::processEvents() () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#8  0x08067ada in startTV() () at main.cpp:98
#9  0x08067b3f in TVMenuCallback(void*, QString&) (data=0x838eb18, 
selection=@0x83a6718) at main.cpp:112
#10 0x400a5893 in ThemedMenu::handleAction(QString&) (this=0x83a65e0, 
action=@0x83c947c) at themedmenu.cpp:1417
#11 0x400a4eee in ThemedMenu::keyPressEvent(QKeyEvent*) (this=0x83a65e0, 
e=0xbffff330) at themedmenu.cpp:1339
#12 0x403fc34c in QWidget::event(QEvent*) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#13 0x40364c19 in QApplication::internalNotify(QObject*, QEvent*) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40364511 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#15 0x40300556 in QETWidget::translateKeyEvent(_XEvent const*, bool) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#16 0x402fbdb9 in QApplication::x11ProcessEvent(_XEvent*) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#17 0x402fb8cf in QApplication::processNextEvent(bool) () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#18 0x40366270 in QApplication::enter_loop() () from 
/usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40548aa3 in QDialog::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x0806878d in RunMenu(QString) (themedir=Cannot access memory at address 
0x0
) at main.cpp:197
#21 0x08069178 in main (argc=1, argv=0xbffff8d4) at main.cpp:272
#22 0x40a08082 in __libc_start_main () from /lib/i686/libc.so.6


I'd also consider possible heat induced CPU errors, but I'd think
other processes would also have problems, and ver .7 was very stable.
I double checked what was in my last patch update, and qt is the same
as another machine that was not patched, so it didn't change.
I'm going to fire it up on my other dual cpu machine (2x1000P3)
and see if it also has problems.

Brian


On Wednesday 05 March 2003 10:11 am, Isaac Richards wrote:
> On Tuesday 04 March 2003 10:45 pm, Brian Foddy wrote:
> > I'm starting to wonder if this might be some reentrant / multi-threaded
> > bad behavior.  The machine is a 2 cpu Pentium II-450.  Will I get
> > enough debug info if I turn on the full optimization with the -g flag?
> > I'd really like to get the resolution back up a bit.
>
> Hmm.. what version of Qt are you using?  It could very well be a
> concurrancy issue in the QSocket stuff.
>
> Isaac
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev