Date: Thu, 30 Jan 1997 09:44:55 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Joaquin Enriquez Beltran <enriquez AT student DOT uni-kassel DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: BIG PROBLEM
In-Reply-To: <32eea957.1567796@news.hrz.uni-kassel.de>
Message-ID: <Pine.SUN.3.91.970130093929.17132L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Wed, 29 Jan 1997, Joaquin Enriquez Beltran wrote:

> After compiling the program the first time it runs, there are no problems
> and everything runs corectly.
> But the following times I execute the program it ends with this message:
> 
> Exiting due to signal SIGFPE

Please run symify on the crash traceback and post the annotated traceback
produced by symify (you will have to compile with -g to get source line
numbers).  Without seeing that information, I would guess that your
program has a bug which leaves the FPU in a state where the next
invocation causes an FP exception.  I suggest experimantiong with the
program's code until you find the fragment which, if removed, makes this
program go away.  Then try to understand why that fragment has that
effect, or post the fragment here if you can't figure it out. 

An alternative would be to reset the FPU state at the program's exit.  
Look up the functions `_clear87' and `_control87' in the libc docs.