Date: Wed, 6 May 1998 16:47:35 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "J.C. Austin" <j DOT c DOT austin AT chem DOT keele DOT ac DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Compiles OK but fails on execution
In-Reply-To: <E0yX2Vj-0000VZ-00@owat.kis.keele.ac.uk>
Message-ID: <Pine.SUN.3.91.980506164134.2627C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 6 May 1998, J.C. Austin wrote:

> I've searched for "environ.lst" using explorer and it doesn't seem to exist
> anywhere on the hard drive.

You need to create it, by typing this:

	set > environ.lst

> Also I'm not sure where to find the output of go32-v2.

go32-v2 is a program.  Run it from the DOS prompt with no arguments and 
it will print the available memory amount.

However, judging by the crash traceback, the above doesn't seem to matter 
in your case.  Your program generates a floating-point exception by doing 
some illegal floating-point operation, like dividing by zero, computing a 
square root of a negative number, or treating an integer like a floating-
point number.

Section 9.2 of the DJGPP FAQ list explains how to convert the funny 
numbers printed when the program crashes into a human-readable 
description of where the crash happens.  You will then need to debug your 
program at the locus of the crash.  If you can't figure it out, post the 
output of symify and the fragment(s) of your program where symify says 
the program bombed.