[mythtv-commits] Ticket #1942: mythtv-0.19_p9163-r1 backend crash
MythTV
mythtv at cvs.mythtv.org
Mon Jun 12 01:15:07 UTC 2006
#1942: mythtv-0.19_p9163-r1 backend crash
-----------------------+----------------------------------------------------
Reporter: anonymous | Owner: ijr
Type: defect | Status: closed
Priority: minor | Milestone:
Component: mythtv | Version:
Severity: medium | Resolution: invalid
-----------------------+----------------------------------------------------
Comment (by buzz at oska.com):
[I post this here, since the 'anonymous' poster doesn't give their name,
or whether they are on any mythtv email lists......]
Maybe I can help interpret Isaac's comment... "need backtrace" means:
"Without a backtrace provided by the original poster, I am unable to
diagnose this problem further, and until then I will set it as 'invalid'
or 'closed' so that other developers know not to spend their time trying
to look into it further."
It also means:
"Could the original poster please provide a backtrace."
From the wiki: "Your best bet for getting help determining the cause of
the problem is to download the myth source code and compile it yourself in
debug mode, then run it with gdb, the GNU debugger. Only with a backtrace
can the developers really help you if your setup is causing Myth to
segfault."
See: http://mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2"
--
Ticket URL: <http://cvs.mythtv.org/trac/ticket/1942>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list