Hi! > 2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos <ceho...@ag.or.at>: > > > > First, please understand that so far, no ABI breakage between > > FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of > > non-public api (that we decided to work-around for 3.1.1). > > OK, then assume that Kodi uses non-public API and the rebuild > made kodi use the latest ABI.
I don't know! I just wanted to point out that so far, the "bugs" that were worked-around in FFmpeg 3.1.1 were bugs in other applications. I still do not understand completely: Is the crash still reproducible after recompiling Kodi or not? > Can I somehow find easily the places where the non-public API is used? I don't know but... > > Am I correct that no backtrace was provided for this issue? > > Yes, AFAIK. ... adding a backtrace should work fast, no? If another developer looks at the backtrace, he might know what the issue is. > > But even with a backtrace, I fear a bisect may be necessary. Bisecting FFmpeg takes less than 20 minutes here, I know it would take you longer but if the backtrace does not help, this is the only way to find out what the issue is. I can try helping to create a specific configure line to speed up the backtrace. Carl Eugen
