Re: XtRemoveTimeOut() with value of 0 accvios under 7.3-2, but not
- From: cook@xxxxxxxxxxxxxxxx (George Cook)
- Date: 10 May 06 19:33:18 EDT
In article <1147298610.745795.260710@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, davidc@xxxxxxxxxxxx writes:
Based upon my reading of XtRemoveTimeout() (regulat X-Windows stuff),
the program is doing something it shouldn't. The argument to
XtRemoveTimeout is a TimerID, and shouldn't be 0. It should be a
non-zero value returned from XtAppAddTimeOut(), where a 0 return
indicates that the timeout was not set (and therefore there is nothing
to remove).
That being said, I wouldn't expect XtRemoveTimeout to crash on a value
of 0, either...
Yes, zero shouldn't crash it, but the crash may not be specific to VMS.
A Google search turned up a similar crash on IRIS systems back in 2001.
Zero was also known to cause crashes way back in X11R3. All the code I
have ever seen which uses XtAppAddTimeOut either validates the timer
or has a safety check for zero.
George Cook
WVNET
.
- Follow-Ups:
- References:
- Prev by Date: Re: XtRemoveTimeOut() with value of 0 accvios under 7.3-2, but not under 7.1-2
- Next by Date: Re: SGI files for chapter 11
- Previous by thread: Re: XtRemoveTimeOut() with value of 0 accvios under 7.3-2, but not under 7.1-2
- Next by thread: Re: XtRemoveTimeOut() with value of 0 accvios under 7.3-2, but not
- Index(es):
Relevant Pages
|
