On Fri, 2013-12-20 at 15:40 -0500, Tyson Whitehead wrote:
> I'm presuming this maybe means the AMD GLX implementation has some sort of
> buggy shared state between displays that is tripping it up when the number of
> screens differs? Any thoughts?
By a lot more stepping through code, I've extracted the essence. Call
glXChooseFBConfig on both displays and it blows up on the second one.
#include <error.h>
#include <X11/Xlib.h>
#include <GL/glx.h>
int main() {
int attribs[] = {
GLX_DEPTH_SIZE, 1, GLX_STENCIL_SIZE, 1,
GLX_RED_SIZE, 1, GLX_GREEN_SIZE, 1, GLX_BLUE_SIZE, 1,
GLX_USE_GL,
GLX_RENDER_TYPE, GLX_RGBA_BIT,
GLX_X_VISUAL_TYPE, GLX_TRUE_COLOR,
None
};
Display* vnc_display;
Display* gl_display;
GLXFBConfig* vnc_configs;
int vnc_configs_number;
GLXFBConfig* gl_configs;
int gl_configs_number;
if ( !(gl_display = XOpenDisplay(":0")) )
error(1, 0, "XOpenDisplay failed for GL display...");
if ( !(vnc_display = XOpenDisplay(0)) )
error(1, 0, "XOpenDisplay failed for VNC display...");
if ( !(gl_configs = glXChooseFBConfig(gl_display, 0,
attribs, &gl_configs_number)) ||
gl_configs_number < 1)
error(1, 0, "glXChooseFBConfig failed for GL display...");
XFree(gl_configs);
if ( !(vnc_configs = glXChooseFBConfig(vnc_display, 0,
attribs, &vnc_configs_number)) ||
vnc_configs_number < 1)
error(1, 0, "glXChooseFBConfig failed for VNC display...");
XFree(vnc_configs);
XCloseDisplay(vnc_display);
XCloseDisplay(gl_display);
return 0;
}
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
VirtualGL-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/virtualgl-users
