Re: EU 3.0.1 -- there's probably a bug in there somewhere
- Posted by Robert Craig <rds at RapidEuphoria.com> Feb 01, 2007
- 710 views
Andy Serpa wrote: > 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? Yes, there were changes in subroutine call/return to support multitasking. These changes can affect programs even if they don't use multitasking. If you are doing recursion, that might be of particular interest in solving this. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com