From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP tools and utilities SIGFPE'ng after Floating Exception
Date: Sun, 15 Nov 1998 10:43:28
Organization: Aspen Technology, Inc.
Lines: 16
Message-ID: <364eb050.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 981111165804 DOT 5508E-100000 AT is> <364CE415 DOT DB9AAFD0 AT cartsys DOT com>
NNTP-Posting-Host: dmcap2.aco.aspentech.com
X-NewsEditor: ED-1.5.8
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> > This is a known problem in some environments.  The DJGPP startup code
> > doesn't clear the FPU and leaves the Invalid exception unmasked.  So when
> > a previous program left the FPU in a mess, and the OS didn't clean up (I
> > think Windows is sloppy in this regard), the next program crashes during
> > startup.

> Now, it seems to me I've asked this before, but I've forgotten the
> answer.  Why don't we reset the FPU at startup, shutdown, or in the
> default SIGFPR handler?

Actually we do reset the FPU at startup during the detection phase.  The
problem noted is a bug in Windows which only appears when certain software
is installed on the machine which changes it's behavior.  There is no 
workaround for this - we've tried - the only fix is to remove the software
on that particular machine which is breaking Windows.  This is NOT a 
DJGPP problem ...