[fleixi]

I have problem adding anything to the videodatabase on gentoo using kodi v18.

I using an arm system and on an other image running debian with compiled kodi v18 i had no problems.

Everytime i add something to the videodatabase and switch back to the mainview of the skin kodi is freezing and killed after some minutes by the system. After that im not able to restart kodi again (freezing while showing the bootsplash) until im removing /home/****/.kodi/userdata/Database/MyVideo***.db

This is my debugcrashlog while adding something: https://pastebin.com/Su2Uj5hq
This is my debugcrashlog restarting kodi with damaged db: https://pastebin.com/txD9xhUp

[DaVu]

gdb not installed, can't get stack trace.

Not that I'm able to help for gentoo, but at least I would suggest to install gdb to get more infos.

[mkortstiege]

Right, a proper stack trace might show what or where it bails out.

[fleixi]

Ok i have had time to install gdb and this is my new crashlog:

https://pastebin.com/F30jFLL1

This time i have added my music to the database.

[asavah]

This stacktrace is pretty much useless.
You need to build a debug version of kodi and avoid stripping it.
On a side note: do you pass any CFLAGS/CXXFLAGS ?
Building Kodi for ARM with -O2/-O3 could cause it to crash depending on gcc version (I remeber having this issue at least with gcc 5.x)

[fleixi]

Ok i will look into building debugbuild in gentoo but this would take some time

Yes im using custom cflags/cxxflags: "-O2 -pipe -march=native -mcpu=cortex-a15.cortex-a7 -mtune=cortex-a15.cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -fomit-frame-pointer"

Everybody on my armdevice (OdroidXu4) is using this flags but i will try disabling -O2 for the next build. Im using gcc 5.xx at the moment to. I could switch to gcc 6.x if i should.

[asavah]

You cflags are wrong.
If you use native - don't force mcpu, gcc will try to detect your cpu/arch automatically, if it does not - remove native and set march/mcpu/mtune as you see fit.

Read https://wiki.gentoo.org/wiki/GCC_optimization OVERoptimization can do more harm than good.

> Im using gcc 5.xx at the moment to. I could switch to gcc 6.x if i should.
That's not that simple, c++ abi changes between gcc major versions, you may need to have to recompile everything on your system that's written in c++

What's the board?

[fleixi]

Here is my next errorlog: https://pastebin.com/KzbkFUEF (debug enabled, no stripping)

i have build it with this flags:

CFLAGS="-O1 -pipe -march=native -mfpu=neon-vfpv4 -mfloat-abi=hard -ggdb"
CXXFLAGS="${CFLAGS}"

https://wiki.gentoo.org/wiki/Upgrading_GCC say that from gcc 5.1 version onward, GCC uses a forward-compatible ABI but i have compiled it with gcc 5.x, same as the rest of the system

Im using a Odroid Xu4 (http://www.hardkernel.com/main/products/...3452239825)

[fleixi]

I have found an "workaround". If i compile kodi with gcc6 not gcc5.4 the error is gone.

I dont know if this is a bug needed to report and where to report it.

[asavah]

I have found an "workaround". If i compile kodi with gcc6 not gcc5.4 the error is gone.

I dont know if this is a bug needed to report and where to report it.

AFAIK the problem with gcc 5.x ARM and Kodi 17 has been known for some time, I'm too lazy to search for the relevant threads on this and other forums (eg arch linux arm forums).
on x86/x86_64 Kodi 17 built with gcc 5.x works just fine ...
I stumbled into it while cross-compiling for rpi, workaround that worked for me was to remove -Ox flags.

Pfft, it's difficult, kodi devs may say (and they probable would be right) that it's gcc bug because 4.[8-9].x , 6.x and 7.x work just fine.
gcc devs probably would ask for a simple example reproducing the bug, because going through all the code of such a HUGE piece of software as Kodi would take enormous amount of time

A very skilled developer with deep knowledge of both Kodi and gcc willing to do all the hard work and submit a proper bug report to gcc bugzilla would be needed.

Currenly I'm building Kodi master (Leia) with gcc 7.1.x for ARM, cmake buildsystem now sets -O3 automatically, no weird crashes.