• Adam Jackson's avatar
    _XDefaultIOError: Do better at detecting explicit shutdown · 5538b3e4
    Adam Jackson authored
    Currently, when the X server crashes or a client is disconnected with
    XKillClient, you get a somewhat confusing error message from libX11
    along the lines of:
    
    XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
          after 98 requests (40 known processed) with 0 events remaining.
    
    What's happening here is the previous recvmsg has thrown EAGAIN, since
    the socket is non-blocking. In this case, check whether the socket has
    any more data to read, and if not treat it like EPIPE.
    Signed-off-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
    5538b3e4
Name
Last commit
Last update
include Loading commit data...
m4 Loading commit data...
man Loading commit data...
modules Loading commit data...
nls Loading commit data...
specs Loading commit data...
src Loading commit data...
.gitignore Loading commit data...
AUTHORS Loading commit data...
COPYING Loading commit data...
Makefile.am Loading commit data...
NEWS Loading commit data...
README.md Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
cpprules.in Loading commit data...
docbook.am Loading commit data...
x11-xcb.pc.in Loading commit data...
x11.pc.in Loading commit data...