Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!converse
From: converse@EXPO.LCS.MIT.EDU (Donna Converse)
Newsgroups: comp.windows.x
Subject: Re: X protocol errors message interpretation?
Message-ID: <9002162333.AA24320@expo.lcs.mit.edu>
Date: 16 Feb 90 23:33:05 GMT
References: <6846.25dae293@swift.cs.tcd.ie>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 47


> Can someone tell me where I can find what each of these mean, please?

>   X protocol error: BadIDchoice, invalid resource ID chosen for this connection.

	In the protocol section within "X Window System - C Library and Protocol 
	Reference" by Scheifler	Gettys and Newman, or in your X protocol 
	documentation which accompanies	the release, see the section on Errors for
	a description of the IDChoice error.  The definition of an X resource is
	given in the glossary.

>   Major opcode of failed request: 1 (X_CreateWindow)

	The protocol request which generated the error message is given here.
	A discussion of the protocol request is in the section on Requests,
	and in Appendix A of the above book there is a table which shows which
	protocol requests are generated by wich Xlib functions, so that you can 
	correlate the request to an Xlib function call.

	I can tell you now that the problem occured in an argument to 
	XCreateSimpleWindow or XCreateWindow which was either a window, a 
	pixmap, a cursor, or a colormap.  

>   Minor opcode of failed request: 0

	Not very interesting, since this is not an extension.  The role of the
	minor opcode is mentioned in the protocol document, the section on
	Protocol Formats.

>   Resource id in failed request: 0x16e0169

	Not all protocol errors return resource IDs, but this one does.  This
	is the invalid resource ID.

>   Serial number of failed request: 87
	
	The 87th request sent to the server is the one that failed.

>   Current serial number in output stream: 93

	The 93rd request to the server has already been made (but not serviced).

You can figure all this stuff out using the table of contents, the index,
and the glossary.  

Donna Converse
converse@expo.lcs.mit.edu