Lately I did the following:
gdb --pid=pid /usr/local/bin/mythbackend
And got this
(gdb) bt
#0 0xffffe410 in ?? ()
#1 0xbffff6d8 in ?? ()
#2 0x0810d7bc in ?? ()
#3 0x0810d638 in ?? ()
#4 0xb68ccfd1 in select () from /lib/tls/libc.so.6
#5 0xb6cfee8a in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#6 0xb6d69e51 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#7 0xb6d69c96 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#8 0xb6d5394f in QApplication::exec () from /usr/lib/libqt-mt.so.3
#9 0x08081699 in main (argc=4, argv=0xfffffdfe) at main.cpp:587
The BE didn't respond to the FE anymore and stayed in the select.
What can I do in gdb to find some answers.
----- Original Message -----
From: "Mark Weaver" <[EMAIL PROTECTED]>
To: "Development of mythtv" <[email protected]>
Sent: Saturday, September 03, 2005 2:51 AM
Subject: Re: [mythtv] [BUG?] Threading / Sockets problem with masterand
slavebackends
Unfortunately when it happend i wasn't running the backend under gdb so i
could not get a backtrace.
Use attach <PID> in gdb.
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
