OpenEuphoria

Re: Running safe.e ???

• Posted by Robert Craig <rds at RapidEuphoria.com> Sep 21, 2003
• 441 views

Derek Parnell wrote:
> So it seems that I'm running the official safe.e and it still works. 

OK, now I see the problem...

You ran the example using ex.exe, whereas Bernie and I
ran it with exw.exe. The bug happens with exw.exe
because the bug is in a section of safe_address()
that is only executed when "edges_only" is 1 (TRUE).
In 2.4 Official release I decided that edges_only = 1
should be the default for WIN32 programs since they often
deal with memory blocks that were not allocated by Euphoria's
allocate(). When edges_only is 1, safe.e only concerns itself
with checking for corruption around the edges of blocks
allocated by allocate(), and it ignores any foreign blocks
that were not from allocate(). Different code is executed.
Try the same example with exw and you should see the
false-alarm bug.

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