[mythtv-commits] Ticket #10775: Segfault in mythbackend (libQtCore.so.4.7.4)
MythTV
noreply at mythtv.org
Mon Jun 18 04:02:04 UTC 2012
#10775: Segfault in mythbackend (libQtCore.so.4.7.4)
----------------------------------------------+----------------------------
Reporter: ajm1@… | Owner:
Type: Bug Report - Crash | Status:
Priority: minor | infoneeded_new
Component: MythTV - General | Milestone: unknown
Severity: medium | Version: 0.25-fixes
Keywords: mythbackend, segfault, libQtCore | Resolution:
| Ticket locked: 0
----------------------------------------------+----------------------------
Comment (by ajm1@…):
An additional observation to share. As noted before the segfault is only
hit when the backend is started with an initscript. If the backend is
started from a shell or within GDB, I am unable to hit the segfault.
The command line given when starting the backend from a shell matches the
command line used within the initscript - with the exception of the start-
stop-daemon. Could this be related???
To test this theory, I did invoke the backend once from a shell using the
start-stop-daemon command line and I '''did hit the segfault'''
Invocation from command line:
{{{
/mythtv/latest/bin/mythbackend --daemon --loglevel debug -v system
--syslog local7 --pidfile /var/run/mythtv/mythbackend.pid --noupnp
}}}
Invocation from initscript:
{{{
start-stop-daemon --start --pidfile /var/run/mythtv/mythbackend.pid--chuid
mythtv --nicelevel 0 --exec /mythtv/latest/bin/mythbackend -- --daemon
--loglevel debug -v system --syslog local7 --pidfile
/var/run/mythtv/mythbackend.pid --noupnp
}}}
--
Ticket URL: <http://code.mythtv.org/trac/ticket/10775#comment:12>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list