On 2/28/11 6:20 PM, Nathan Kidd wrote:
> On 11-02-28 07:04 PM, DRC wrote:
>> I'm not following how you ascertained that the issue was between WINE
>> and the 3D X server.
>
> Sorry, I didn't mention that part. I ran against an in-house X server
> with tracing enabled and examined the trace. No GLX, and more
> importantly, no X errors returned at all. Therefore it had to be the 3D
> X Server.
I've encountered situations before in which a particular GLX call will
only be sent to the 2D X server if the GLX extension is detected on it.
I can't easily imagine a scenario in which a GLX call would be sent to
the 3D X server unless VirtualGL was sending it. If the error is
reproducible with Exceed 3D, it would be a worthwhile experiment to try
disabling GLX support in the latter and see if the error goes away.
Something else I've started to notice in recent nVidia drivers is that,
if I run remotely using the VGL Transport, I get the following warning:
Xlib: extension "NV-GLX" missing on display "{client_display}".
The nVidia drivers do some hooking of functions at the low level, so
it's possible that they are hooking an Xlib call and making a GLX call
from within the body of the Xlib call. They may very well be using a
private symbol for the hooked GLX call, or the dynamic link order may be
such that VirtualGL is not catching it.
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users
