Linux Regular crashes, finally some effort to post crash logs
#1
Hi there, I'm one of those lazy people who wants everything working but lacks motivation to post crash logs.
Well today finally decided to get off my bum and post some.

My setup is
Kodi Helix/RC1/Ubuntu 14.04 latest kernel as of today.
These are my last 3 crash logs, would really appreciate some info on finding out what's going on.

I seem to experience crashes specifically when accessing "recordings" sub menu from the TV item on the home screen. The crash appears in the form of no list of recordings showing up and all GUI elements disappearing apart from the main Kodi background image and box only responding to a soft reset/no response from keyboard/remote. I also experience some crashes when watching live-tv out of the blue for no reason every couple of days.
The crashes have been consistent regardless of using the official mainline tvheadend client or the new one in the tvheadend subforum. They have also been consistent regardless of which version of XBMC/Kodi/tvheadend backend, TV tuner verified working/numerous drivers tested.http://pastebin.com/H7pJaf3G

http://pastebin.com/4bzATe1Q

http://pastebin.com/H7pJaf3G

http://pastebin.com/0k9kTKWD
Reply
#2
please install gdb. without it the logs are pretty useless sadly.
Reply
#3
and enable debugging...
Reply
#4
Thanks for the pointers.
I'll do that now and leave the thread float away.

Will respond once have some proper logs Smile

Thanks again,
Reply
#5
Right, I did as asked installed gdb, enabled debug logging and enabled trace logging for tvheadend too.

Kodi RC2 just crashed when I selected "TV" in the main homescreen menu (Live-TV)

I have a log file but its 190MB in size in the Kodi temp directory kodi.old.log
There is no crashlog at all like there usually is without debug enabled in the home/xbmc directory

...Bit confused, do I open the 190MB text file and cut/paste?

Thanks Smile
Reply
#6
bump Smile
Reply
#7
restart xbmc with debugging enabled and produce a smaller crashlog.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#8
(2014-12-08, 17:08)fritsch Wrote: restart xbmc with debugging enabled and produce a smaller crashlog.

Thanks for posting fritsch, the problem is that the crash isn't repeatable and usually only happens after the box being on a couple of days. Would it not be simply a case of opening the massive debug log and skimming off the latest entries?
I'll try opening it in a suitable text viewer anyway.
Reply
#9
Pastebin only the part of the backtrace then?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply

Logout Mark Read Team Forum Stats Members Help
Regular crashes, finally some effort to post crash logs0