abmg@cathedral.cerc.wvu.wvnet.edu (Aliasghar Babadi) (04/30/91)
Hi, What are these errors for? Xlib: sequence lost (0x10055 > 0x5d) in reply type 0x7! Xlib: sequence lost (0x10055 > 0x7a) in reply type 0x7! Thanks in advance.
mouse@lightning.mcrcim.mcgill.EDU (der Mouse) (05/04/91)
> 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. Check your malloc areas for overruns, check for storing through uninitialized automatic pointer variables.... What the error actually means is that Xlib sees things happening out of sequence. X requests and replies have sequence numbers, which have to be in sequence, you see.... der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu
randy@erik.UUCP (Randy Brown) (05/07/91)
> > 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