Kodi Community Forum

Full Version: Crash without stacktrace in crash log
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hello everybody,

I have noticed multiple times crash when using PVR with tvheadend when switching the channel.
I check always the crash log but these times there is no stack trace.

How could be this possible?

I am on Helix 14.1rc1.
Any hints from the team?
Ask in the PVR subforum (hts, tvheadend, etc.).
moved the thread
But how can Kodi "crash" without a stack trace?
In case it's related, watch this thread, and maybe follow some advice there:

http://forum.kodi.tv/showthread.php?tid=213283

It might also be helpful if you can at least name your OS and backend, or perhaps even post a debug log. It saves a lot of guesswork.
Alright, so one idea would be to test the merge request ...

Here my crash log: http://pastebin.com/4RWT7XrG

I can give you 5+ looking like each other.
Okay, you're on Debian Jessie and are using tvheadend, correct? Might need to drag negge into this, then - post in that other thread if he doesn't spot this.

And grab a full debug_log (wiki), please, not just the crash log.
Is it possible to disable the debug overlay?
Mostly it occurs when I doesn't calculate on the crash.
Switch it OFF in the GUI, but then switch it ON in advancedsettings.xml, as described here:

http://kodi.wiki/view/Advancedsettings.xml#loglevel

So you want <loglevel hide="false">1</loglevel>, i.e. show it in the GUI as an option, but don't show the debug info on screen.
Have you installed gdb? You'll need that for stack traces to work. Without the trace the log is mostly useless.
(2015-01-03, 02:01)Prof Yaffle Wrote: [ -> ]Switch it OFF in the GUI, but then switch it ON in advancedsettings.xml, as described here:

http://kodi.wiki/view/Advancedsettings.xml#loglevel

So you want <loglevel hide="false">1</loglevel>, i.e. show it in the GUI as an option, but don't show the debug info on screen.
Thanks, works like a charm.

(2015-01-03, 10:38)negge Wrote: [ -> ]Have you installed gdb? You'll need that for stack traces to work. Without the trace the log is mostly useless.
Yes of course, otherwise there would be a mesasge in the crashlog:
Code:
############### STACK TRACE #################
gdb not installed, can't get stack trace.
############# END STACK TRACE ###############

Or there is a mistake in the implementation, now.

Code:
[email protected]:~# dpkg -l | grep gdb
ii  gdb                                  7.7.1+dfsg-5                      amd64        GNU Debugger
ii  gdbserver                            7.7.1+dfsg-5                      amd64        GNU Debugger (remote server)
@H3llGhost do you have a log which contains a trace?
In general yes, but with the Helix 14.1-RC1 Git:692cfba it doesn't work anymore.

With 14.0rc3-Helix-xbmc-2.4.4-Helix:
Code:
############## Kodi CRASH LOG ###############

################ SYSTEM INFO ################
Date: Wed Dec 24 15:52:02 CET 2014
Kodi Options:
Arch: x86_64
Kernel: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08)
Release: Debian GNU/Linux 8 (jessie)
############## END SYSTEM INFO ##############

############### STACK TRACE #################
=====>  Core file: /home/xbmc/core (2014-12-24 15:52:01.787664836 +0100)
        =========================================
[New LWP 5592]
[New LWP 5523]
...
################# LOG FILE ##################

15:51:40 T:140399648581696  NOTICE: special://profile/ is mapped to: special://masterprofile/
15:51:40 T:140399648581696  NOTICE: -----------------------------------------------------------------------
15:51:40 T:140399648581696  NOTICE: Starting Kodi (14.0-RC3 Git:692cfba). Platform: Linux x86 64-bit
15:51:40 T:140399648581696  NOTICE: Using Debug Kodi x64 build
15:51:40 T:140399648581696  NOTICE: Kodi compiled Dec 22 2014 by GCC 4.9.1 for Linux x86 64-bit version 3.16.7 (200711)
15:51:40 T:140399648581696  NOTICE: Running on Debian GNU/Linux 8 (jessie), kernel: Linux x86 64-bit version 3.16.0-4-amd64
15:51:40 T:140399648581696  NOTICE: FFmpeg statically linked, version: 14.0rc3-Helix-xbmc-2.4.4-Helix
15:51:40 T:140399648581696  NOTICE: Host CPU: Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz, 4 cores available
...
Any reason you can't use the final code versus rc-anything? Just in case you're experiencing a problem that's already been addressed...
Pages: 1 2