From:	"Lawrence Rust" <lvr AT nospam DOT softsystem DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
References:	<q78f9.1851$Yc7 DOT 106506 AT newsfep2-gui> <3d7d6309 DOT sandmann AT clio DOT rice DOT edu> <3D7E5533 DOT D4C4DE0 AT phekda DOT freeserve DOT co DOT uk>
Subject:	Re: SIGALRM signal handler doesn't save FPU state
Lines:	21
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID:	<h%Ff9.678$3h7.42668@newsfep2-gui>
Date:	Wed, 11 Sep 2002 12:43:00 +0100
NNTP-Posting-Host:	62.253.142.12
X-Complaints-To:	abuse AT ntlworld DOT com
X-Trace:	newsfep2-gui 1031744589 62.253.142.12 (Wed, 11 Sep 2002 12:43:09 BST)
NNTP-Posting-Date:	Wed, 11 Sep 2002 12:43:09 BST
Organization:	ntl Cablemodem News Service
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

"Richard Dawe" wrote...
> Hello.
>
> Charles Sandmann wrote:
> [snip]
> > > Perhaps the FAQ could be updated to include this info or even
> > > better if libc could include this for async signals.
> >
> > I'd vote yes for documentation (info libc someplace).  No for FAQ, since
> > it's the first time it's come up that I know about, and Eli's busy :-)
>
> I'll try to add a note to the docs in CVS, next time I have my DJGPP hat
on.

A note in the libc docs for setitimer or signal would be ideal.  Might save
someone a deal of time.  Thanks.

-- Lawrence Rust, Software Systems, www.softsystem.co.uk
The problem with Windows XP: http://www.arachnoid.com/boycott

- Raw text -