Message-Id:	<360AB3C2.41EE@cableol.co.uk>
Date:	Thu, 24 Sep 1998 22:04:02 +0100
From:	Allens <allen DOT asjp AT cableol DOT co DOT uk>
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
Subject:	Re: HELP!!!URGENT!!
References:	<6teh3g$a10$1 AT evia DOT ccf DOT auth DOT gr> <360A9896 DOT E03EADC2 AT informatik DOT tu-chemnitz DOT de>

Alexander Gottwald wrote:
> 
> Bk\sgr Watfgsta}qou wrote:
> 
> > Exiting due to signal SIGFPE
> > Floating Point exception at eip=0000193c
> > eax=00003020 ebx=0004f0c0 ecx=0004d533 edx=00000009 esi=00000054
> > edi=0000eb00
> > ebp=0004e950 esp=0004e850
> > program=C:\WINDOWS\EPIV6M~1\PHYSICS\MUON\SIMUL2.EXE
> > cs: sel=00af  base=835f8000  limit=0005ffff
> > ds: sel=00b7  base=835f8000  limit=0005ffff
> > es: sel=00b7  base=835f8000  limit=0005ffff
> > fs: sel=0087  base=00020fb0  limit=0000ffff
> > gs: sel=00c7  base=00000000  limit=ffffffff
> > ss: sel=00b7  base=835f8000  limit=0005ffff
> > Call frame traceback EIPs:
> >   0x0000193c
> >   0x00001cb6
> >   0x000016d7
> >   0x00002e62
> >
> > Does anyone know what this means???
> >
> > Thank you,
> > Vlasis Hatzistavrou.
> 
> The numbers are from the register dump. They show the register contents
> when the error occured.
> 
> It seems like a floating-point number has an overflow. Check if
> somewhere a floating point number is divided by zero or some very small
> numbers.
> 
> This is the best hint i can give.

And type symify simul2.exe next time the crash happens.  This will give 
you the last few functions called leading up to the crash

- Raw text -