From: leathm AT solwarra DOT gbrmpa DOT gov DOT au (Leath Muller)
Message-Id: <199708120236.MAA23398@solwarra.gbrmpa.gov.au>
Subject: Re: djgpp vs lahey fortran
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Tue, 12 Aug 1997 12:36:54 +1000 (EST)
Cc: leest96 AT dong DOT snu DOT ac DOT kr, djgpp AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.970811172617.7651J-100000@is> from "Eli Zaretskii" at Aug 11, 97 05:30:46 pm
Content-Type: text
Precedence: bulk

> The `symify' utility included with DJGPP should let you translate this=20
> traceback into human-readable listing of file names and line numbers that=
> =20
> will lead you to the point where the problem happens.  After that, you=20
> should debug your program to see why did this error happen.

Symify should be more accurate IMHO in pinpointing the location of the FP
error. I had a lot of trouble working out FP errors because I had large
chunks of assembly statements throughtout my code... All symify did was
tell me the location of the group of FP instructions where the problem
occured... ie:

	asm volatile {		<- symify points here
		....
		200 asm lines... :)
		....
	}

Leathal.