Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!iuvax!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!m.cs.uiuc.edu!carroll
From: carroll@m.cs.uiuc.edu
Newsgroups: comp.windows.x
Subject: Re: Orphaned Response
Message-ID: <26900124@m.cs.uiuc.edu>
Date: 23 Aug 90 02:53:00 GMT
References: <171113@<1990Aug6>
Lines: 13
Nf-ID: #R:<1990Aug6:171113:m.cs.uiuc.edu:26900124:000:621
Nf-From: m.cs.uiuc.edu!carroll    Aug 22 21:53:00 1990


/* Written 11:59 pm  Aug  6, 1990 by kucharsk@number6.Solbourne.COM in m.cs.uiuc.edu:comp.windows.x */
In article <1990Aug6.171113.12758@hod.uit.no> roar@hpserv1.uit.no (Roar Steen) writes:
 >I keep getting these messages from X:
 >
 >Xlib:  sequence lost (0x23294 > 0x23293) in reply type 0x1!

The most frequent cause of these errors is a bug in the use/allocation of
pointers.
/* End of text from m.cs.uiuc.edu:comp.windows.x */
I believe that you can get the error if you enter X event reading routines
more than once, for example attempting a read, getting and signal, and then
trying to read in the signal handler.