Guys, something wrong is going on in E17. Specifically inside e_icon.c and e_int_menus.c. We are calling specific evas object function that are not supposed to be called on other type of evas object. Like evas_object_image_fill_set on some smart object. Evas protect bad developper from calling function on the wrong object, but this can hide some bigger bug. So it's a bad habit to rely on evas to protect us from doing nasty thing.
Right now I don't have time to dig this, but it's easy to reproduce. First disable evas magic debug check (--disable-evas-magic-debug to configure). Start E17 with valgrind (enlightenment_start -valgrind=3), go in the configuration dialog, show some config dialog with icons, then go back to the main menu, and move your cursor over the entry, it will show you some error in valgrind output at some point. If some people have time to find where it come from, that would be nice :-) Happy debug, PS: I added a bug in the bug tracker, #396, but I decided to write this mail, to be sure that every EFL developper know about this issue and will less likely add the same kind of bug in the futur. -- Cedric BAIL ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
