From: leathm AT solwarra DOT gbrmpa DOT gov DOT au (Leath Muller)
Message-Id: <199703042347.JAA11434@solwarra.gbrmpa.gov.au>
Subject: Re: Allegro perspective-correct texture mapping
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Wed, 5 Mar 1997 09:47:57 +1000 (EST)
Cc: ovek AT arcticnet DOT no, djgpp AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.970304134700.12059M-100000@is> from "Eli Zaretskii" at Mar 4, 97 01:47:48 pm
Content-Type: text

> I suggest you first verify that the problem is indeed an overflow (it
> might be some other FP-related trouble, like passing an invalid
> argument to a math function).  Once you did that, there are three ways
> around this that I can think of:
 
Just to extend on what Eli has said, probably the easiest and fastest way
to check that your actually overflowing the stack is to try and run the
program in a debugger, put a breakpoint at the instruction before the
offending instruction, and when the program breaks at the breakpoint, check
the stack. If it is full before an fld, then its an overflow problem.
If the stack isn't full, then its another problem altogether... :) Just
so you know, I use FSDB because I know how to... ;)

Leathal.