I'm trying to fix a crash in e17 that seems to always happen the first time I run it after bootup. This problem has existed for at least 2 years, but I'm only looking at it now, as most other bugs have now been fixed.
I followed instructions on the e17 debugging page, and rebuilt all the libs with -g for debugging symbols. I ran e17 and captured some good info in gdb. The problem only happens the first time e17 is run after bootup. It cycles through 3 successive "white rectangles of death" before disabling modules and finishing startup. After this, if I quit X11 and restart it, no more crash. If I reboot, it crashes again. I captured the gdb backtrace, the pastebin is here: http://pastebin.com/xskYpRxt The code that crashed looks like it is related to the mmx module of evas. So I recompiled evas without mmx, and recompiled ecore and e. I tried it again. e17 crashed in the same place, but with a non-mmx equivalent of the same operation. The pastebin is here: http://pastebin.com/YDteFFzG It's strange that it only happens the first time I run it after reboot. Any help very much appreciated! -Dave PS Please don't be scared off by this being on MacOS - it is Darwin/BSD under the hood! ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
