[Xcb] [PATCH xcb/libxcb] Fatal error message when we close libX11 window application

[Uli Schlachter]

Am 26.05.2015 um 22:00 schrieb robert somerville:
> Hi Uri:

Hi Lobelt,

> here is the message when we hit the close button: ( I can send screen
> captures, if you wish  ( how ?) ) :
> 
> XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server
> "cgy530ws:0.0"
>       after 1304786 requests (1300490 known processed) with 0 events
> remaining.
> 
>> more tttt.cxx
[...]
>   // Draw the line
>   for(;;) {
>     XDrawLine(dpy, w, gc, 10, 60, 180, 20);
>     // Send the "DrawLine" request to the server
>     XFlush(dpy);
>   }
> 
>   // Wait for 10 seconds
>   sleep(10);
> }
[...]

This code uses Xlib instead of XCB, so this mailing list isn't really the right
place. Also, what behavior would you expect from this code? The above is an
endless loop, so it can't really be quit. What Xlib does to get out of it is to
exit(). Also, you don't implement ICCCM's WM_DELETE_WINDOW protocol, so the WM
will use KillClient to "close" your window. This is where the IO error comes
from in the first place.

I still don't really see what bug you are referring to. If you want to get rid
of the error message, use the XSetIOErrorHandler() call that is already present
in your code and make myIOXError return without printing a backtrace.

Uli
-- 
<alanc> I think someone had a Xprint version of glxgears at one point,
    but benchmarking how many GL pages you can print per second
    was deemed too silly to merge