On Fri, 6 Jan 2017 02:21:10 -0600 Jeff Hoogland <jeffhoogl...@gmail.com> said:
> Having some users report segfaults with our E17 fork using the latest EFL > under our Ubuntu 16.04 base. > > Had someone run a back trace and post it here > <http://forums.bodhilinux.com/index.php?/topic/14036-moksha-segfault/?p=102195>. > Looks like it is dying in the EFL somewhere? I'm honestly not great at > debugging C code - anyone help point me in the right direction? the backtrace is "long after the bug already happened". the malloc heap is corrupt. libc has detected something is wrong and aborted during an allocation. what caused the issue is unknown. it could be efl. could be e. could be libpng. could be just about anything. it is unknown. the best way to find out who is doing this is to use valgrind to run execution and it can trap out-of-allocation writes and tell you the exact point where this write is done. that would provide the info needed to fix if it isn;'t already fixed in git efl - if the issue is there. if the issue is in e17 it'd point that out too. or wherever else it is. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
