Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!dimacs.rutgers.edu!bcm!etaylor
From: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Newsgroups: comp.windows.x
Subject: Re: core dump in XtRemoveTimeOut
Message-ID: <2770@gazette.bcm.tmc.edu>
Date: 15 Nov 90 16:20:10 GMT
References: <1990Nov13.202552.25425@aplcen.apl.jhu.edu>
Sender: usenet@bcm.tmc.edu
Reply-To: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)
Organization: Baylor College of Medicine, Houston, Tx
Lines: 9
Nntp-Posting-Host: wilkins.iaims.bcm.tmc.edu


We had this happen too and were able to conclude that it was the fault of Xw.  They were not completely correct in handling TimeOuts correctly.  i.e.  They either removed the IntervalId twice or they forgot to remove it when the widget was destroyed.  I can't remember which.

	I use the XtAddTimeOut and RemoveTimeOut with no problems.
--
					Eric Taylor
					Baylor College of Medicine
					etaylor@wilkins.bmc.tmc.edu
					(713) 798-3776