OpenEuphoria

Re: How to handle crashes?

• Posted by jbrown105 at speedymail.org May 31, 2003
• 507 views

No, restoring the variables and context is overkill.

I see that saving the current variables (in full) and context (i.e. which
statements were executed) into an error file, is a good idea. It would be a
great aid to debugging. But I fail to see the need to RESTORE the variables.

jbrown

On Fri, May 30, 2003 at 06:52:57PM -0500, gertie at visionsix.com wrote:
<snip> 
> It's rather acceptable, somewhat needed, and overkill for your purposes. 
> What if you have a crash every other month, and you can't find the bug? Like 
> this new bug in mirc 6.03:
> 
>  set -u0 %walkcolor1 
> $gettok(%colors1,$rand(1,$len(%colors1)),$asc(%comma))
>  
> 
> Those functions return at different times, and occasionally %walkcolor1 will 
> be $null. But a stepper ide like Eu won't catch it, even if mirc had one. But 
> storing the vars did catch it, leading to code like this:
> 
>   :regetwalkcolor1
>   set -u0 %walkcolor1 
> $gettok(%colors1,$rand(1,$len(%colors1)),$asc(%comma))
>   if ( %walkcolor1 == $null ) { goto regetwalkcolor1 }
> 
> If you have a cgi box that crashes once a month, you could rebuild to the 
> moment before the crash, possibly stepping back in time thru the execution.
> 
> Kat
> 
> 
> 
> TOPICA - Start your own email discussion group. FREE!
> 
> 

-- 
 /"\  ASCII ribbon              | http://www.geocities.com/jbrown1050/
 \ /  campain against           | Linux User:190064
  X   HTML in e-mail and        | Linux Machine:84163
 /*\  news, and unneeded MIME   |