Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: polstra!jdp@uunet.uu.net (John D. Polstra)
Newsgroups: comp.sys.sun
Subject: Re: 68881/Mcrt1.o problems with setitimer()
Keywords: Software
Message-ID: <268@polstra.UUCP>
Date: 9 May 89 07:29:20 GMT
References: <499@ircam.UUCP>
Sender: usenet@rice.edu
Organization: Polstra & Co., Seattle
Lines: 12
Approved: Sun-Spots@rice.edu
Original-Date: 28 Apr 89 03:05:01 GMT
X-Sun-Spots-Digest: Volume 7, Issue 278, message 3 of 24

(In article <499@ircam.UUCP> (v7n255) metcalf@ircam.ircam.fr (Chris Metcalf)
wrote about setitimer behavior which seemed to depend on the selected floating
point option.  He gave a sample program which worked with -fsoft but not
with -f68881.)

The itimerval structure has an "it_interval" field which you have not
initialized.  In your program, that field contains stack garbage which
varies depending on what has happened in the runtime kickoff code.  Stick
"static" on the front of your declaration for "itv" and the problem goes
away.

	John Polstra	jdp@polstra.UUCP	...uunet!practic!polstra!jdp