With the help of nVidia, I was able to get to the bottom of what's going on with WINE 1.3.11+. In fact, it has nothing to do with WINE. Any application that attempts to call glXSwapIntervalSGI() with a Pbuffer current will cause nVidia GLX to trip a BadWindow error. This has been the case at least since 195.xx.xx (didn't test anything before that.)
I'm not really sure whether I'd call this a driver "bug". It depends on your point of view. On the one hand, it is understandable that glXSwapIntervalSGI() would have no meaning with a Pbuffer, but IMHO, the underlying driver should just make it a no-op in that case. The spec for glXSwapIntervalSGI() does not say that it is an error to call it on a Pbuffer, although it is understandably a meaningless operation. In any sense, this confirms that interposing on glXSwapIntervalSGI() and making it a no-op in VGL 2.2.1 is absolutely the right approach. DRC ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
