OpenEuphoria

Re: How to handle crashes?

• Posted by gertie at visionsix.com May 30, 2003
• 431 views

On 30 May 2003, at 17:45, jbrown105 at speedymail.org wrote:

> 
> 
> On Fri, May 30, 2003 at 10:03:48PM +0100, Pete Lomax wrote:
> > 
> > 
<snip>
> > 
> > Pete
> > 
> > PS One perfectly acceptable method, in my eyes, would be to write a
> > (massive) ex.err file and then re-invoke the interpreter to parse that
> > file to initialise those global variables. I would not want or expect
> > it to be fast.
> 
> I find it not acceptable or needed. This is definately overkill.

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