Robert Lunnon <[EMAIL PROTECTED]> writes:
> read(11, 0x7FD5F7AC, 8) Err#11 EAGAIN
> XIO: fatal IO error write(2, " X I O : f a t a l ".., 21) = 21
> 0 (write(2, " 0 (", 3) = 3
> Error 0write(2, " E r r o r 0", 7) = 7
> ) on X server "write(2, " ) o n X s e r v e".., 15) = 15
> :0.0write(2, " : 0 . 0", 4) = 4
> "
> write(2, " "\r\n", 3) = 3
> after write(2, " a f t e r ", 12) = 12
> 0write(2, " 0", 1) = 1
> requests (write(2, " r e q u e s t s (", 11) = 11
> 0write(2, " 0", 1) = 1
> known processed) with write(2, " k n o w n p r o c e".., 23) = 23
> 0write(2, " 0", 1) = 1
> events remaining.
> write(2, " e v e n t s r e m a".., 20) = 20
> _exit(1)
>
> The last X IO operation before the fatal error was called was a read n the X
> pipe which return error EAGAIN
The problem is that Xlib doesn't see the right errno value. It's a
threading issue.
--
Alexandre Julliard
[EMAIL PROTECTED]
