Date: Mon, 9 Jun 1997 17:43:47 -0700 (PDT)
Message-Id: <199706100043.RAA07810@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Symify crashes in Windows Dos box
Precedence: bulk

In relation to the message to which I just replied ("Re: possible bug" from
tudor AT cam DOT org), I ran the program:

>> #include <stdio.h>
>> #include <string.h>
>> int main(void)
>> {
>>   double n;
>>   memset(&n,0xFF,sizeof(double));  /* contrived, sure */
>>   printf("%f\n",n);
>> }

It crashed, as it claimed. Then, when I ran symify to find just where,
symify crashed. This was in a Win 3.1 Dos box. Symifying works fine under
plain Dos. The traceback is included here for your viewing pleasure :)
------- cut -------
Exiting due to signal SIGFPE
Floating Point exception at eip=00004fd2
eax=00000000 ebx=00000000 ecx=0005704c edx=00000033 esi=000507a2 edi=000109de
ebp=000509be esp=000507a2 program=C:\DJGPP\BIN\SYMIFY.EXE
cs: sel=00a7  base=80c6d000  limit=0005ffff
ds: sel=00af  base=80c6d000  limit=0005ffff
es: sel=00af  base=80c6d000  limit=0005ffff
fs: sel=0087  base=00010090  limit=0000ffff
gs: sel=00bf  base=00000000  limit=ffffffff
ss: sel=00af  base=80c6d000  limit=0005ffff

Call frame traceback EIPs:
  0x00004fd2
  0x00003aa9
------ cut ------
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?
--------------------
Nate Eldredge
eldredge AT ap DOT net