E17 is overall working well with OSX. There's one important bug that needs to be fixed before it's ready for a binary release.
On OSX, e17 crashes only on the first run after reboot. The "white rectangle of death" appears, and clicking "continue" a few times eventually brings up a working e17. However that's too buggy for a binary release. Just to be clear, if I quit e17 and restart, no crash. If I reboot, it crashes again in the same place. The crash only happens on the 1st run after reboot, and is reproducible. The gdb trace is here: http://pastebin.com/JzeA0xw6 The trace looks like something in mmx. If I compile ecore without mmx support, it crashes in the same place, but with equivalent non-mmx calls. That means the problem is probably higher up in the call stack, but I'm not sure where to look. This bug has been around for a while and I have posted before. Posting again hoping someone can help take a look at it. I can #irc if someone wants. If there's anything else useful I could capture pls let me know. I have valgrind, though I'm not sure how to effectively capture e17 in valgrind since it's never called directly - the wm is started with "enlightenment_start". Dave ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
