On 17. Oct 2010, at 23:13, Matthew Dawson wrote: > I ran into this issue myself. It appears that the ati drivers expect to be > able get the current X11 display when you make certain glx calls. The > backtrace looks like it travels through glew into the ati driver (free here), > and then the ati driver tried to contact the X11 server using the X11 display > connection in the GL context. Since no GL context exists, the X11 display > connection is null, thus a null dereference happens and it all blows up. I > believe the issue is in the driver, not eq. As a workaround, I think you > could create a temporary GL context that would allow for the driver to > execute its queries.
It seems then that the GLXEW initialization should happen like the WGLEW initialization in WGLPipe: open temp context, query extensions, delete temp context. That also means moving the GLXEWContext to GLXPipe, which makes the whole construct more symmetric. Any volunteers for this task? Cheers, Stefan. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
