Date: Mon, 1 May 2000 12:03:20 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr>
cc: djgpp-workers AT delorie DOT com
Subject: Re: interrupt 0x75 limitation in Win95 ?
In-Reply-To: <200004271332.PAA01783@cerbere.u-strasbg.fr>
Message-ID: <Pine.SUN.3.91.1000501120302.9191K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 27 Apr 2000, Pierre Muller wrote:

>    When I run a simple code that creates a FPU exception by a 
> 
>    j:=j/e;
> 
>   where j and e are double and e has 0.0 value;
> 
>   I get a nice FPU exception,
> but if I redirect the output of this code using DJGPP redir executable 
> it does not work anymore :(
> 
>   The exception seems to be sent to the redir executable rather than to the
> correct executable !

Yes, it looks like Windows doesn't support FP exceptions in nested
DPMI programs; the exception seems to be delivered to the parent
instead.

If the parent program is a 16-bit real-mode program or COMMAND.COM,
the FP exception does happen in the program that divides by zero, but
if COMMAND.COM is invoked from a DJGPP program, the exception is also
lost.