RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler) (08/31/88)
Date: 30 Aug 88 22:34:23 GMT
From: poisson.usc.edu!wescheng@oberon.usc.edu (Wesley Cheng)
Due to the asynchronous nature of X (being that it is a client-server
model using events to communicate), I have often had trouble finding
the source of run time errors.
Have you tried running in synchronous mode, using "-synchronize" in a
toolkit client's command line? Or setting _Xdebug to 1 from the
debugger before starting the client? This should help a lot.
Is there
also a way to have the server tell us exactly which parameter is out
of range rather than just printing that something is wrong and exiting?
No, there isn't, sorry. If you run in synchronous mode and look at
the arguments to the offending call, and consult the protocol spec,
it should be fairly straightforward to figure out.