On 3/24/11 3:45 PM, Nathan Kidd wrote: > From those messages it seems that a4 does some internal checks and > doesn't like it when VGL redirects and/or modifies certain GLX state. > > You can run with +tr (VGL_TRACE) option to see if you can find out what > VGL was doing when a4 became unhappy. To determine this the writes from > a4 and VGL trace need to be in order, but depending on where a4 writes > to (stdout/stderr) they may not be written that way.
If my hypothesis is correct and a4 is doing the same thing a3 was doing, then VirtualGL is never getting loaded. Thus, you would never see any tracing output from it. ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/virtualgl-users
