> Things like these: > > > ***** Ewl Developer Warning ***** : > To find where this is occurring set a breakpoint > for the function ewl_print_warning. > This program is calling: > > ewl_widget_type_is(); > > With the parameter: > > widget > > being NULL. Please fix your program. > > > I guess that some of the things are simply outdated by your recent > developments. > :( If you have some time, keeping them up-to-date would be good. >
I'm seeing some warnings by a couple of widgets. Some I haven't got to yet. I'm working through the list. I haven't seen any segvs yet, so I'm not sure what that is. If you want to get a back trace run ewl_test in gdb and then do r --ewl-segv <test> and it will segv as soon as a warning is printed. Without a backtrace it's pretty much impossible to know where these are coming from. dan ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
