[Libff-devel] Re: Xlib errors

[<jg...@pa...>]

Typically, this happens when the request stream gets corrupted.
The X server keeps track of how many requests it has seen and returns this
sequence number in replies.

This can happen a number of ways:
	1) multithreaded application not using locking properly (Xlib has
	locking for MT use, but you have to turn it on).
	2) memory trashing bug
	3) Xlib or X server error.
	4) some corruption in the data stream between the X server and client.

3) and 4) is quite rare: I'd suspect 1 or 2 to start, until proven otherwise.
			- Jim


--
Jim Gettys
Cambridge Research Laboratory
Compaq Computer Corporation
jg...@pa...