Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!lll-winken!sun-barr!ccut!kogwy!wnoc-tyo-news!sragwa!sran124!srava!erik
From: erik@srava.sra.co.jp (Erik M. van der Poel)
Newsgroups: comp.windows.x
Subject: Re: X protocol errors message interpretation?
Message-ID: <3895@srava.sra.co.jp>
Date: 16 Feb 90 13:29:01 GMT
References: <6846.25dae293@swift.cs.tcd.ie>
Reply-To: erik@sra.co.jp (Erik M. van der Poel)
Organization: Software Research Associates, Inc., Japan
Lines: 17

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

If you look up BadIDChoice in the Xlib document, you will find that it
is an error that cannot normally occur. A colleague of mine bumped
into this error and found that a call to setitimer() caused it. This
function causes a signal to be delivered to the program, and if this
happens in the middle of an Xlib operation, Xlib can get confused.

Try looking for `setitimer' or `SIG' in the program sources.

If you do find a setitimer() you should probably consider re-coding it
to use XtAppAddTimeOut().
-- 
Erik M. van der Poel                  erik@sra.co.jp             (Japan)
SRA, 1-1-1 Hirakawa-cho, Chiyoda-ku   erik%sra.co.jp@uunet.uu.net  (USA)
Tokyo 102 Japan. TEL +81-3-234-2692   erik%sra.co.jp@mcvax.uucp (Europe)