[mythtv-users] "Suggested next mythfilldatabase" date in the past
Michael T. Dean
mtdean at thirdcontact.com
Mon Jan 25 02:44:12 UTC 2010
On 01/24/2010 12:22 AM, Rich Wilson wrote:
> On Sat, Jan 23, 2010 at 5:22 AM, Christopher X. Candreva wrote:
>> I think I missed the obvious. There IS still a mythfilldatabase process
>> hainging around, from Jan 21 at midnight.
> I am seeing the same thing. Does the following gdb backtrace help anyone
> what's causing this? This is the backtrace of the hung mythfilldatabase run
> started about a week ago.
> (something like >sudo gdb /path/to/mythfilldatabase 11042 2>&1 | tee mfdb)
> GNU gdb (GDB) 7.0-ubuntu
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu".
> For bug reporting instructions, please see:
> Reading symbols from /usr/bin/mythfilldatabase...(no debugging symbols
> Attaching to program: /usr/bin/mythfilldatabase, process 11042
> Reading symbols from /usr/lib/libmythtv-0.22.so.0...(no debugging symbols
> Loaded symbols for /usr/lib/libmythtv-0.22.so.0
> <snip: a lot of lines deleted>
> Reading symbols from /lib/tls/i686/cmov/libnss_files.so.2...(no debugging
> symbols found)...done.
> Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2
> 0x00c80422 in __kernel_vsyscall ()
> (gdb) bt
> #0 0x00c80422 in __kernel_vsyscall ()
> #1 0x00869e15 in pthread_cond_wait@@GLIBC_2.3.2 ()
> from /lib/tls/i686/cmov/libpthread.so.0
> #2 0x03850e67 in QWaitCondition::wait(QMutex*, unsigned long) ()
> from /usr/lib/libQtCore.so.4
> #3 0x0384fec9 in QThread::wait(unsigned long) () from
> #4 0x00325af1 in MythSocketThread::ShutdownReadyReadThread() ()
> from /usr/lib/libmythdb-0.22.so.0
> #5 0x00325b8f in ShutdownRRT() () from /usr/lib/libmythdb-0.22.so.0
> #6 0x064d805f in ?? () from /lib/tls/i686/cmov/libc.so.6
> #7 0x064d80cf in exit () from /lib/tls/i686/cmov/libc.so.6
> #8 0x064bfb5e in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> #9 0x0804f831 in ?? ()
> (gdb) q
> A debugging session is active.
> Inferior 1 [process 11042] will be detached.
> Quit anyway? (y or n) Detaching from program: /usr/bin/mythfilldatabase,
> process 11042
It would be easier to tell with a full backtrace (as at
http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2 ), but it looks
like it may be due to the socket issues that seem to be plaguing some
(mainly *buntu?) users.
More information about the mythtv-users