OpenEuphoria

Re: BREAKing into Euphoria

• Posted by CChris <christian.cuvier at a?ri?ulture.gouv.fr> Sep 12, 2007
• 2591 views

Andy Drummond wrote:
> 
> Pete Lomax wrote:
> > 
> > 
> > I got some "interesting" results (random crashes mainly) from this, however
> > enough of it works to show that something is possible (comments, Rob?):
> > Maybe there is a generic problem with trace in call_back routines??
> > ........ 
> > I suspect that if you could somehow call the trace(1) in HandlerRoutine but
> > not then trace any lines in that code, it might actually work.
> > 
> > When not interpreting source, or under an allow_break(False), then Ctrl
> > Break
> > should not attempt to fire up the trace window, otherwise it should.
> > I don't think changing Ctrl C is a good idea, too easy to accidentally hit,
> > plus eg Edita happily uses it for Copy w/out problems as is.
> > 
> > Regards,
> > Pete
> 
> Yes, well, I see what you mean now. The control-C or control-Break keys do
> indeed break the program but there is no evidence that it ever reaches the
> code you sent. So ... not much further forward.
> Andy

You can use the Eu-in-Eu eu.ex program - perhaps renamed to .exw - to run your
code, after modifying it so as it tells you (probably by writing to a debug file)
whenever it enters or exit a routine, in the opPROC() procedure from execute.e.
If your code is quite linear in shape, you can , at the same time, do some
printf() to the same debug file at critical points.

CChris