Mass version move, cvs -> git

What GPU ? Does it still happen with recent checkout ?

I'm using an Intel G45, but I get the same error when using the software rasterizer. 

This is still a problem with Mesa git as of a few days ago.

System environment:
-- chipset: G45 / ICH10R
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- Machine or mobo model: Asus P5Q-EM
-- Display connector: DVI
-- KMS: enabled
-- xf86-video-intel: 6361c3b9af39265df9222b1f3b6fb9c4197087c1
-- xserver: 1.6.3
-- mesa: 72052210516b4cb0e082e0c56822cd33b1562630
-- drm: d74c67fb13d8c3e8c2e5968d827285d147a5dfc0
-- kernel: 2.6.31-rc6 (debian)

(Answering myself here)

The "No matching FBConfig" comes from the application, not Mesa. It seems it's asking for GLX_PBUFFER_BIT and pbuffers isn't that well supported?

For reference, this is the whole list of visuals asked for:

        int attList[] = {
                GLX_BIND_TO_TEXTURE_RGBA_ATI, True,
                GLX_RENDER_TYPE,   isFloatFormat(texture.format)? GLX_RGBA_FLOAT_ATI_BIT : GLX_RGBA_BIT,
                GLX_X_RENDERABLE,  True,
        	GLX_DRAWABLE_TYPE, GLX_PBUFFER_BIT,
                GLX_X_VISUAL_TYPE, GLX_TRUE_COLOR,
                GLX_CONFIG_CAVEAT, GLX_NONE,
                GLX_RED_SIZE,      bpc,
                GLX_GREEN_SIZE,    (nCh > 1)? bpc : 0,
                GLX_BLUE_SIZE,     (nCh > 2)? bpc : 0,
                GLX_ALPHA_SIZE,    (nCh > 3)? bpc : 0,
                GLX_DEPTH_SIZE,    24,
                GLX_STENCIL_SIZE,  0,
                GLX_DOUBLEBUFFER,  False,
                None
        };

Created attachment 35279 [details]
backtrace

With the Xserver patched for pbuffer support, I can run the Windows version of the demo. The Linux version no longer complains about missing fbconfigs but segfaults instead.

This is the line which is causing the problem:

 glXBindTexImageATI(display, (GLXPbuffer) textures[textureID].renderTargetData[0], GLX_FRONT_LEFT_ATI);

Full backtrace is attached.

It segfaults because Mesa doesn't implement GLX_ATI_render_texture and the demo doesn't check for the extension and just uses it. Closing as it's not our bug.