2009-10-09, 17:51
The log is absolutely useless in these cases. We need a stacktrace for there to be any hope in fixing this.
althekiller Wrote:The log is absolutely useless in these cases. We need a stacktrace for there to be any hope in fixing this.
CapnBry Wrote:You will also probably have to turn on cores before launching xbmc from that terminalRun it till it locks then do the killall above. You should see "Segmentation fault (core dumped)" in the terminal window and there should be a core.XXXX file in that directory.Code:ulimit -c unlimited
xbmc
althekiller Wrote:You can kill xbmc with "killall -SEGV xbmc.bin" to generate a core file then examine it for deadlock (obviously the problem here) with gdb. You may need to launch XBMC from the console for the core to be generated properly.
Redth Wrote:Ok, the Getting a Stacktrace section of the wiki is not very informative... sorry i'm a newb to this...
How exactly do I go about getting a stack trace? I'm now using the SVN PPA repo and have installed xbmc-common-dbg... I have version 9.04.3+svn23539-jaunty1 installed right now..
I'd be more than happy to submit a stack trace, but I'm not sure where I would find it...
Redth Wrote:Well, as you said, the system gets locked up... doing the killall -SEGV from a ssh session does NOT work....
So, not sure how we're going to diagnose this..
Redth Wrote:doing the killall -SEGV from a ssh session does NOT work....Try
pkill -SIGSEGV xbmc.bin
Maxim Wrote:Tryinstead.Code:pkill -SIGSEGV xbmc.bin
jverdeyen Wrote:any reason why I should go back from Hardy to Jaunty?