[Xcb] mesa +xcb = assertion death

Jeremy Kolb jkolb at brandeis.edu
Wed May 4 23:05:29 PDT 2005

Jamey Sharp wrote:
> On Wed, 2005-05-04 at 23:48 -0400, Jeremy Kolb wrote:
>>Jeremy Kolb wrote:
>>>On another note... I looked in the xserver's glx and there was no *2... 
>>>so I added that and checked and it now looks correct wrt 
>>>numProps/numVisuals.  Didn't seem to fix anything though.
>>Okay, now that I fixed that (filed a bug report for them too) glxinfo 
>>actually runs!  This is exciting...
> That *is* really exciting! You rock.
Thanks! But it was a team effort, never would have found out why it was 
dying without you. :)
>> but now I get that BadLength error 
>>with glxgears in X_GrabKey and X_UnGrabKey
>>With NVIDIA drivers and Mesa/X11-xcb:
>>X Error of failed request:  BadLength (poly request too large or 
>>internal Xlib length error)
>>   Major opcode of failed request:  33 (X_GrabKey)
>>   Serial number of failed request:  19
>>   Current serial number in output stream:  19
>>With indirect Mesa and X11-xcb it's X_UnGrabKey (30).  Guess I'll look 
>>into those.

Ok this vanished (dunno how or why) and things seem to actually be 
working.  I can now run glxgears and in one single function it says "XCB 
Enabled", which means that we have a very preliminary support for single 
ops using XCB :)

Trying to find a good test program for the single requests.  Almost 
everything is done with the render request which I haven't touched yet.


More information about the xcb mailing list