On 17/06/15 03:10, Carsten Haitzler wrote: > On Tue, 16 Jun 2015 22:13:27 +0100 pietran...@gmail.com (Stefano M.) said: > >> Carsten Haitzler (The Rasterman) <ras...@rasterman.com> writes: >> >>> [...] >>>> Hope this helps, >>> >>> nope. doesn't help. :) >> >> Too bad... let me know if there's anything I can do though. >> >> Best, > > right now you can't i think - beyond noting that a recompile fixes things on > an > efl upgrade... which implies an abi break. what is the break though. one thing > that might begin to help is a backtrace with full debug symbols from the > crash. > a bt full - maybe a vlagrind run/trace. >
No insights. I also don't know what API you use in terminology. While the ABI report is not much, according to it we don't have ABI breaks except for one minor one we fixed between 1.13.0 and 1.13.1 (or something like that, maybe it was 1.12.0 that broke it). This is however from the top of my head, haven't looked at them again. I also wonder which versions are involved. Was git ever involved? As archers we should be able to easily reproduce it with such info. -- Tom. ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
