Date: Tue, 10 Jun 1997 11:19:25 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Nate Eldredge <eldredge AT ap DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Symify crashes in Windows Dos box
In-Reply-To: <199706100043.RAA07810@adit.ap.net>
Message-ID: <Pine.SUN.3.91.970610111843.3067T-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 9 Jun 1997, Nate Eldredge wrote:

> I might have expected a crash from when symify tries to look at video memory
> (or however it works), but not a SIGFPE! Anybody know anything about
> this/have time to debug it?

IMHO, there's nothing to debug here.  The original program crashes
with SIGFPE because it tries to use garbage as an FP number.  Nothing
new here.  `symify' crashes because Windows doesn't reset the FPU
after the first program crashes; nothing new here either.  I'd guess
any of the following would cause `symify' run without crashing on
Windows also (I didn't actually check this though):

	1) Redirect the original crash traceback to a file or use the
clipboard to put it in a file, then close the DOS box (or reboot the
system, or go to another machine) and invoke `symify' on that file
("symify -i crash-file programname").

	2) Reset the FPU after the crash (e.g. with a program that
calls `_clear87'), then run symify.