[mythtv] [mythtv-commits] Ticket #4238: blootube-wide & video settings: unknown tag image crashes frontend

aaron memoryguy at gmail.com
Thu Nov 29 18:45:32 UTC 2007


On 11/29/07, MythTV <mythtv at cvs.mythtv.org> wrote:
>
>  I don't know why I can't get backtrace. I did svn update, compiled with
>  --compile-type=debug, installed. Both for mythtv and mythplugins trunk.
>  Then restarted backend, followed the instructions in myth manual to take
>  backtrace with gdb, also by giving the commands within gdb, but still I
>  don't get trace! WTF?
>
>  gdb.txt:
>  "
>  Starting program: /usr/local/bin/mythfrontend
>  [Thread debugging using libthread_db enabled]
>  [New Thread -1255392480 (LWP 2330)]
>  [New Thread -1257768048 (LWP 2336)]
>  [New Thread -1266160752 (LWP 2337)]
>  [New Thread -1274553456 (LWP 2338)]
>  [New Thread -1285715056 (LWP 2343)]
>  [New Thread -1313809520 (LWP 2344)]
>  [New Thread -1341473904 (LWP 2349)]
>  [New Thread -1349866608 (LWP 2350)]
>  [New Thread -1358259312 (LWP 2351)]
>
>  Program terminated with signal SIGKILL, Killed.
>  The program no longer exists.
>  No stack.
>  "
>

The process is being killed somehow, it's not really "crashing."
SIGKILL is not catchable, thus the process is ended before gdb can get
a chance to pull out any useful information. I'm not aware of all the
situations where processes might get killed by the system, but one of
them is running out of memory. Perhaps check the system logs to see if
there are any messages about being Out of Memory and Killing process
mythfrontend.

-- 
aaron

"Oh oh oh. I'm incoherent with excitement. Please tell me what fascinating
bit of badger-sputumly inconsequential trivia you will assail me with next."
        -- Arthur Dent


More information about the mythtv-dev mailing list