www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/03/11/02:17:33

Date: Mon, 11 Mar 1996 08:08:51 +0100 (MET)
From: erik AT tntnhb3 DOT tn DOT tudelft DOT nl (Erik Luijten)
Subject: Re: floating p. exception behaves strange
To: djgpp AT delorie DOT com (djgpp)
Message-id: <9603110708.AA12518@tntnhb3.tn.tudelft.nl>

Charles Sandmann wrote:

> When I tried to code a workaround - it would sometimes generate a second
> SIGFPE just trying to re-initialize the FPU immediately after the exception!
> (causing a loss of the FPU signal information and other problems).
> 
> I'm tired of writing code to work around bugs for a company which makes
> Billions of dollars selling buggy software.  You paid for W95, try to get
> Microsoft to send you a patch.  Else, establish a signal handler for SIGFPE
> and try to handle the nested exceptions which get generated, and do what
> you feel needs to be done.

Oh, but you shouldn't misunderstand me! I am not asking you to write a
workaround for this. I just noticed the behavior and wanted to be sure that
the problem was not in djgpp. This is apparently not the case, so for me the
case is "solved".

Best regards,

Erik


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019