I was playing with OpenGL last weekend, and I was able to crash DRI again with TCL enabled, crash disappeared when I disabled TCL (r200 hardware, Athlon CPU).
I've noticed that it's much easier to crash by rendering GL_LINES or GL_LINE_STRIP than GL_POINTS or GL_QUADS. I run my application with valgrind and noticed that there are some invalid writes of size 4 (one float?) in glVertex3f code, but I couldn't find exact code (last level of backtrace was "??"). Have you tried debugging DRI with valgrind? Is it "clean" for you? I also tried to profile DRI with callgrind (http://kcachegrind.sourceforge.net/cgi-bin/show.cgi), it was very useful, because I could see what calls what in Mesa/drm and what takes most of the time. How can I debug DRI crash? I don't see anything in logs, can I use gdb somehow to write where it crashed? I read that second computer may be useful for debuging locked system, but what exactly should I check after network login? And isn't possible to write that to log automaticaly after some keys combination / joystick command? -- Free Software - find interesting programs and change them NetHack - meet interesting creatures, kill them and eat their bodies Usenet - meet interesting people from all over the world and flame them Decopter - unrealistic helicopter simulator, get it from http://decopter.sf.net ------------------------------------------------------- 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 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
