Posts: 7,638
Joined: Jun 2011
Reputation:
285
install gdb, there is no backtrace in your crashlog.
Since there is zero hint whats going on from the log, I'm guessing its the usual gcc 5.2 issue.
You made sure your whole distro was rebuilt against the new ABI, did you?
Posts: 7,135
Joined: Oct 2012
un1versal
Out of Memory (1939–2016)
Posts: 7,135
Try making sure your user is able to create core files in /home
Put the following at the bottom of your /etc/sysctl.conf
Code:
kernel.core_uses_pid = 1
kernel.core_pattern = /home/core.%e.%p.%s.%t
fs.suid_dumpable = 1
and in your /etc/security/limits.conf
Code:
kodi soft core unlimited
save both files and reload sysctl or reboot.
Then see if when kodi next crashes the crashlogs should contain the stacktraces else no idea.
Posts: 968
Joined: Nov 2011
Reputation:
10
giaur
Posting Freak
Posts: 968
I'm confused. I did all you proposed and now kodi does not crash anymore. After above changes made, kodi all the time exits without segmentation fault. There was no any system updates applied. It looks weird for me.
Posts: 7,135
Joined: Oct 2012
un1versal
Out of Memory (1939–2016)
Posts: 7,135
2015-08-25, 16:00
(This post was last modified: 2015-08-25, 16:07 by un1versal.)
In your case limits.conf should be michal not kodi
Code:
michal soft core unlimited
And dont use Debian packages, use your self compiled Kodi, maybe it is related to gcc5, no experience there personally so until we see a stacktrace that's it.
One thing you could try if the above fails, is compiling a nightly that includes
https://github.com/xbmc/xbmc/pull/7376
Posts: 968
Joined: Nov 2011
Reputation:
10
giaur
Posting Freak
Posts: 968
2015-08-25, 18:52
(This post was last modified: 2015-08-25, 19:00 by giaur.)
I reported my own build. But it was built with gcc5, because gcc5 is default compiler in Debian now (at least in Sid).
But, as I wrote above, magically problem is gone now. No crashes so far and I don't understand what happens here
Thanks for hint, indeed I did not put my username there. As soon as I see crash again, we'll se if it helps to capture backtrace
Posts: 7,135
Joined: Oct 2012
un1versal
Out of Memory (1939–2016)
Posts: 7,135
Well none of what I asked you to try would magically fix any Kodi issues.
What I suspect is you have some addon causing this issue, and I base this information on your other thread of yours which were also addons causing those issues.
Posts: 968
Joined: Nov 2011
Reputation:
10
giaur
Posting Freak
Posts: 968
2015-08-25, 19:42
(This post was last modified: 2015-08-25, 19:46 by giaur.)
Hmm my test was performed on clean installation, without any custom addons.
Regarding to Kodi16 nightly... I tried to compile but I was stuck on hell of dependencies, maybe I will try again when have some time. I mean Kodi custom libs, I was unable to compile and install them
Posts: 7,135
Joined: Oct 2012
un1versal
Out of Memory (1939–2016)
Posts: 7,135
When all reasons are exhausted I blame it on Debian.
Posts: 968
Joined: Nov 2011
Reputation:
10
giaur
Posting Freak
Posts: 968
Isn't gcc5 used in Ubuntu as well? If not, it's going to be used in near future
Posts: 7,135
Joined: Oct 2012
un1versal
Out of Memory (1939–2016)
Posts: 7,135
(2015-08-25, 19:42)giaur Wrote: Hmm my test was performed on clean installation, without any custom addons.
Regarding to Kodi16 nightly... I tried to compile but I was stuck on hell of dependencies, maybe I will try again when have some time. I mean Kodi custom libs, I was unable to compile and install them
You didnt read the Docs on github and you should if you are compiling anything.
I'll leave a response to your gcc comments to the pros, no idea if the source needs any fixes for it or if its even gcc or not some Debian quirkiness at play. Since we dont have any stacktraces or any information to go by I doubt you get any answer to hypotheticals.