OpenEuphoria

Re: trace()

• Posted by Robert Craig <rds at RapidEuphoria.com> Oct 04, 2005
• 458 views

Hayden McKay wrote:
> While in a trace session, when we reach the line in our code that caused an
> error the trace screen is closed and the error message is put to the screen
> 
> I think this is a floor in trace() and could be addressed easily. Rather
> than kill the trace screen, leave it open and display the abort error in
> the trace window until the user presses a key. When a key is pushed kill
> the program in the usual manner.
> 
> This will let the user to get a good look at the trace variables at the
> time of a crach before the trace window closes.

Thanks for the suggestion. I understand what you are asking,
but I don't think it's particularly easy to. I guess you'll have to
remember the names of the variables you are interested in,
and look up their values in ex.err. Remember also that you can
trigger a dump into ex.err at any time by pressing the exclamation
key (!) on the trace screen.

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