[mythtv] Unable to hit segfault within GDB, but no problem outside of GDB
A McDermott
list at mcdermotts.ca
Tue May 22 22:20:39 UTC 2012
Have a backend segfault which happens every couple of days. I cannot
provide a backtrace as I only hit the segfault when running outside of
GDB. Is there anything in the available information which can assist
in debug?
Two occurrences.
[42167.238283] mythbackend[1282]: segfault at 48 ip 00007f81b3ff9cbd
sp 00007f81a49aecd0 error 4 in libQtCore.so.4.7.4[7f81b3e7a000+292000]
[490961.484105] mythbackend[32330]: segfault at 48 ip 00007f87709c5cbd
sp 00007f87610b1cd0 error 4 in libQtCore.so.4.7.4[7f8770846000+292000]
I start GDB with:
mythtv at pvr:~# cat /home/mythtv/gdbcommands
handle SIGPIPE nostop noprint
handle SIG33 nostop noprint
set logging on
set pagination off
set breakpoint pending on
break qFatal
set args --loglevel debug --syslog local7 --noupnp
handle SIGHUP nostop
run
thread apply all bt full
set logging off
Normally, initscripts start the backend with the following parameters:
/mythtv/latest/bin/mythbackend --daemon --loglevel debug --syslog
local7 --pidfile /var/run/mythtv/mythbackend.pid --noupnp
More information about the mythtv-dev
mailing list