OpenEuphoria

Re: EU 3.0.1 -- there's probably a bug in there somewhere

• Posted by Andy Serpa <ac at onehorseshy.com> Feb 01, 2007
• 720 views

Robert Craig wrote:
> 
> 
> Yes, I'd like to see it, if you can set up a simple example.
> 
> So far no one has reported any similar crashes to yours.
> If you or anyone else is serious about tracking this down right away,
> you might build a debug version of the exw.exe interpreter,
> or at least one with some added print statements,
> and try to find where exactly in the interpreter it is crashing.
> At a return, there is often some storage recycling which could
> crash if something on the heap has been corrupted (either by the
> user program or the interpreter).
> 
I've been running 3.0.1 for a just a couple weeks -- had no problems with
anything but these most complex programs using lots of memory.  (Had a similar
crash on something else a couple days ago, but didn't bother to track it down.) 
So a "simple example" may be an impossibility.  If I change the order of
statements in the crashing function or just add do-nothing statements (but so
that the logic remains the same), it will still crash, but maybe on a different
call to the function at a different time.

Also, it may be helpful to know that in the ex.err file it produces, all of the
variable values for the function in question are listed as <no value>, so
apparently it is happening as or just after it has dereferenced those.  I assume
something is not getting cleaned up properly.  Have you changed anything along
these lines from v2.5 to 3.0?

I'll see if I can produce a debug version, but it may be beyond me...