Date: Thu, 12 Jun 1997 14:41:36 -0700 (PDT)
Message-Id: <199706122141.OAA12314@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: Symify crashes in Windows Dos box
Cc: djgpp AT delorie DOT com
Precedence: bulk

At 06:20  6/12/1997 +0300, you wrote:
>
>On Tue, 10 Jun 1997, Nate Eldredge wrote:
>
>> >new here.  `symify' crashes because Windows doesn't reset the FPU
>> >after the first program crashes; nothing new here either.
>>
>> Then maybe the handler that aborts the program on receipt of the signal
>> ought to reset the FPU. It seems like a bad idea to leave the system
>> unstable.
>
>It's probably better to do that in the exit code, not in the SIGFPE
>handler (somebody could install a signal handler for SIGFPE that just
>returns, and then the program would leave the FPU scrogged on exit).

Good point. Maybe the best way to do it is add `fclex' somewhere in _exit
(see src/libc/crt0/crt0.S, line 282). Since _exit gets called *anytime* the
program exits (AFAIK), that should take care of it. 

Nate Eldredge
eldredge AT ap DOT net