malc wrote: > 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. You could do what the r300 driver does (which has configurable span locking). If it crashes when doing a swrast fallback, the lock was in r200SpanRenderStart, you can just call UNLOCK_HARDWARE immidiately after LOCK_HARDWARE, and remove the UNLOCK_HARDWARE in r200SpanRenderFinish.
Roland ------------------------------------------------------------------------- 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
