I'm going to try and fix this bug. However, the ONLY way I have found to get into __glXDRIdrawableDestroy is by calling glXDestroyWindow. glXDestroyWindow is part of GLX 1.3, and the current X server do *NOT* support GLX 1.3. Calling glXDestroyWindow is a bug in the application. Crashing because of it is a bug in the driver. How can the application (Wine, in this case) expect anything good to happen when it calls unsupported extension functions?
I'm going to try and fix this bug. However, the ONLY way I have found to get into __glXDRIdrawabl eDestroy is by calling glXDestroyWindow. glXDestroyWindow is part of GLX 1.3, and the current X server do *NOT* support GLX 1.3. Calling glXDestroyWindow is a bug in the application. Crashing because of it is a bug in the driver. How can the application (Wine, in this case) expect anything good to happen when it calls unsupported extension functions?