Hi'all, Is there any progress on solving the savageGetLock() (and most likely related viaGetLock()) crash? This bug has been haunting savage and via users for a long time now. My otherwise trusty Thinkpad T23's crash and burn whenever some program tries to destroy a GL context. In free software this can generally be circumvented by refraining from destroying the context until the program closes, but in close source/proprietary stuff (think Pro/E etc.) this is not possible.
For reference, I'm talking about these bugs: https://launchpad.net/bugs/81889 https://launchpad.net/bugs/90850 https://lists.ubuntu.com/archives/ubuntu-mono/2007-September/008219.html http://bugs.freedesktop.org/show_bug.cgi?id=10191 http://www.google.se/search?q=savageGetLock+OR+viaGetLock+segfault+OR+crash etc... I have not hacked any dri stuff so it would take me some time to get up to snuff wrt these drivers. If there are no takers I'd be willing and hopefully able to give it a go but in that case I'd like some pointers in the right direction. Someone somewhere surely has wondered about these segfaults before... right? Cheers//Frank ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
