OpenEuphoria

Re: 2.4 Official Release - machine level exception

• Posted by Robert Craig <rds at RapidEuphoria.com> Jul 09, 2003
• 515 views

Andy Serpa wrote:
> I still the get a mystery crash once in a while.  I can never isolate or 
> duplicate it precisely (usually random numbers are involved and I can 
> never find a seed that reproduces the problem), but it seems to happen 
> in programs that sum up a large number of floating point values, often 
> incredibly small values, and then do something like invert it.  Can you 
> think of a reason adding up a bunch of floats (there are probably 
> precision issues here) would ever cause a problem?  

No, I haven't come across anything like that.

> Sometimes a number 
> that isn't quite zero is taken to be zero in some operations but not 
> others (precision again, I assume).  What happens if I do 
> 1/not_quite_zero ?

There was a problem in 2.3, fixed in 2.4...

"bug fixed: Translated code compiled with Borland C was not
  producing INF's and NAN's, like Watcom and Lcc. Rather, it was
  crashing when a floating-point overflow (over 1e308), or an
  undefined f.p. result was calculated. The Interpreter Source Code
  was also corrected for those who wish to compile exw.exe
  using Borland. Thanks to Andy Serpa."

I know you are still using 2.3 for some things.
I also noticed that Windows ME provides less
detail when a crash occurs than Win98 did, so you
might not see that it was a floating-point exception.

Regards,
    Rob Craig
    Rapid Deployment Software
    http://www.RapidEuphoria.com