Re: X sequence lost
>>>> "Andy" == Andy Piper
<andy(a)xemacs.org> writes:
Andy> At 06:37 PM 3/25/00 +0100, Michael Sperber [Mr. Preprocessor] wrote:
>
> I see the "async reply" problem mostly upon starting a subprocess,
> like igrep. Could this be related to Ben's subprocess changes?
>
> Xlib: unexpected async reply (sequence 0xd03)!
> Xlib: sequence lost (0x101c2 > 0xd03) in reply type 0x99!
> Xlib: sequence lost (0x10000 > 0xd03) in reply type 0x0!
>
> xemacs: X Error of failed request: 0
> Major opcode of failed request: 3 (X_GetWindowAttributes)
> Serial number of failed request: 0
> Current serial number in output stream: 3331
>
> Anybody got any idea on how I can debug this?
Andy> What happens if you do (x-debug-mode t) and then put a breakpoint in gdb in
Andy> x_error_handler?
Then, the bug doesn't occur anymore, at least as far as I can see. On
the other hand, with (x-debug-mode t), all sorts of other things go
wrong: Half the time, XEmacs can't save files.
--
Cheers =8-} Chipsy
Friede, Völkerverständigung und überhaupt blabla