Hello, Sometimes (in my case quite frequently) Mesa code triggers a hardware exception and the process receives a SIGFAULT/ILL/whatever, normally this is not much of the problem unless it was done while preceding code held a lock, which sadly happens a lot to me.
For instance calling glCopyTexSubImage2D while having GL_FRAGMENT_SHADER_ATI enabled goes through swrast path and crashes becasue one of the pointers to function field is NULL and R200 did a LOCK_HARDWARE before. Ever so helpful SDL when initialized withouyt SDL_INIT_NOPARACHUTE will try to cleanup and hit a deadlock, the stituation when debugging the process with gdb and hitting the aforementioned condition is almost the same - X not responding/updating. For both SDL and gdb X will stop responding to keyboard (the mouse is alive and well though) making debugging/bugreporting impossible. In fact due to the rather "interesting" setup of KVM/usb2ps2 convertors i can't even use magic sysrq to cleanly reboot the system and the only option is to power the machine down in the most brutal way. I was wondering if there's anything that can be done about it (even killing X completely would be a better option that what i have now) -- vale ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
