Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!decwrl!wsl.dec.com!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: X protocol errors message interpretation?
Message-ID: <2795@bacchus.dec.com>
Date: 16 Feb 90 17:37:02 GMT
References: <6846.25dae293@swift.cs.tcd.ie>
Sender: news@decwrl.dec.com
Reply-To: klee@decwrl.dec.com
Organization: DEC Western Software Laboratory
Lines: 21

In article <6846.25dae293@swift.cs.tcd.ie>, gteo@swift.cs.tcd.ie writes:
>   X protocol error: BadIDchoice, invalid resource ID chosen for this
connection.
>   Major opcode of failed request: 1 (X_CreateWindow)
>   Minor opcode of failed request: 0
>   Resource id in failed request: 0x16e0169
>   Serial number of failed request: 87
>   Current serial number in output stream: 93
> 
> Can someone tell me where I can find what each of these mean, please?

Does this always happen?  The IDchoice error is possibly a bug in your
Xlib.  Typically, only the first 2 lines of the error message are
useful.  You can find descriptions of the errors on p. 350-351 of
Scheifler's DP book and in the descriptions of the various Xlib
functions.  The other error data is discussed on p. 346.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee