Newsgroups: comp.windows.x
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!dont-send-mail-to-path-lines
From: randy@erik.UUCP (Randy Brown)
Subject: Re:  xlib error
Message-ID: <9105061716.AA11450@erik.uucp>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Date: 6 May 91 17:16:29 GMT
Lines: 14


> > What are these errors for?
> 
> > Xlib:  sequence lost (0x10055 > 0x5d) in reply type 0x7!
> > Xlib:  sequence lost (0x10055 > 0x7a) in reply type 0x7!
> 
> They are Xlib-internal.  This is almost invariably caused by a wild
> pointer bashing an Xlib-internal data structure. 

I have also seen these on systems complied with -DSTREAMSCONN due to
an error in the readv/writev emulation  routines.  I posted a bug fix
for this some time ago;  it's not in any  of the patches, but I got
the polite message back that the bug was fixed in the "development
environment," so I guess it was real.  ... rb