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?
What happens if you do (x-debug-mode t) and then put a breakpoint in gdb in
x_error_handler? Does this give any clues as to what is triggering it?
andy
--------------------------------------------------------------
Dr Andy Piper
Senior Consultant Architect, BEA Systems Ltd