Message-ID: <372EF63F.F5DBD092@bergamoexport.it>
Date: Tue, 04 May 1999 15:29:35 +0200
From: Federica <ica AT bergamoexport DOT it>
X-Mailer: Mozilla 4.5 [it] (Win98; I)
X-Accept-Language: it
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: HelpMePlease
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

I'v got problems with floating point .
My program crashes (at run time ) if compiled in my machine but runs OK
when compiled in friend of mine one (then my machine can't compile it
well).
I've readed all your FAQ list (great strain for me , I'm italian ) but
it haven't help me.

My machine is a pentium with 32M ram and Win98 (I've tryed also to run
gcc in restarted DOS setting off the windows DPMI and using GWSDPMI but
the problems remain the same ).
I've tryed to compile under -lemu.

that's the crash-output (with -g option and after symify):

Exiting due to signal SIGFPE
Floating Point exception at eip=00002dc9
eax=00000000 ebx=00000000 ecx=0006a410 edx=00054240 esi=0006a400
edi=3fe6a09e
ebp=0005329c esp=00053250 program=C:\MATEO\TESI\EULEROD.EXE
cs: sel=00af  base=82fea000  limit=0006ffff
ds: sel=00b7  base=82fea000  limit=0006ffff
es: sel=00b7  base=82fea000  limit=0006ffff
fs: sel=0087  base=00015b00  limit=0000ffff
gs: sel=00c7  base=00000000  limit=ffffffff
ss: sel=00b7  base=82fea000  limit=0006ffff

Call frame traceback EIPs:
  0x00002dc9   _calutili+1313, line 388 of eulerod.c
  0x0000157b   _main+23, line 100 of eulerod.c
  0x000070b2   ___crt1_startup+138

and that's the go32-v2 output with environ.1st setting :

go32/v2 version 2.0 built Aug 12 1996 22:27:23
Usage: go32 coff-image [args]
Rename this to go32.exe only if you need a go32 that can run v2 binaries
as
 well as v1 binaries (old makefiles).  Put ahead of the old go32 in your
PATH
 but do not delete your old go32 - leave it in the PATH after this one.
Set GO32_V2_DEBUG=y in the environment to get verbose output.

DPMI memory available: 19927 Kb
DPMI swap space available: 9853 Kb

Charles Sandmann wrote me that somthing have corrupted the buint in DPMI
providers way of handling coprocessor events (a windows bug )
That's all ?!?!?!

thank you
Matteo