OpenEuphoria

Re: EuCOM and Interpreter Bugginess

• Posted by Robert Craig <rds at RapidEuphoria.com> Jun 04, 2004
• 793 views

Elliott S. de Andrade wrote:
> There's something very strange going on here. If I run EuCOM.ew (in a 
> program or by itself to test), there are some weird results when there are 
> missing include files. If unicode.ew is missing, it works correctly. Namely, 
> it prints out that it can't find unicode.ew and waits. If, however, 
> unicode.ew exists and variant.ew or comerr.ew do not, the interpreter does 
> not error out properly. Initially, it prints out the name and EUINC path, 
> but before it can print out what the error really is, another machine error 
> occurs. This prints out its own message, which would be alright, but then it 
> procedes to crash entirely, without writing an ex.err.

When a machine-level exception occurs, there is no guarantee that
the interpreter will be able to complete the process of writing
ex.err, without itself crashing. Things may be too corrupted in memory.
Just by trying to unwind the call stack or print a variable,
the interpreter might use a pointer that the application
corrupted. 

Actually, there is always a remote chance that an application
that uses pokes etc, will corrupt things badly enough that 
the interpreter will not be able to terminate properly with an ex.err.
But it's especially likely when a machine-level exception is reported.

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