The Case Of The Runaway Debugger

K nnoydb at
Wed Jul 21 12:32:33 CDT 2004

Actually, I have experienced that error.  I cleared all breakpoints and exited Revolution and it just went away.  

NOTE: Many times it occured in handlers/functionss that I used value() for invocation.



Any resemblance between the above views and those of my
employer, my terminal, or the view out my window are purely
Any resemblance between the above and my own views is non-deterministic.

 The question of the existence of views in the absence of anyone to hold
is left as an exercise for the reader. The question of the existence of
the reader
 is left as an exercise for the second god coefficient. 
(A discussion of non-orthogonal, non-integral polytheism is beyond the
scope of this article.)

 --- On Wed 07/21, Kenneth Rabe < Kenneth.J.Rabe at > wrote:
From: Kenneth Rabe [mailto: Kenneth.J.Rabe at]
To: erik at, use-revolution at
Date: Wed, 21 Jul 2004 07:37:24 -0700
Subject: Re: The Case Of The Runaway Debugger

This is bug 1554.  I've seen it happen most often when using the <br>variable watcher.<br><br>Ken Rabe<br><br>Erik Hansen wrote:<br><br>>although the Trace is OFF, the tracedelay is<br>>set as high as possible, and the breakpoint is<br>>coded in, the Debugger still traces through<br>>script code of its own volition.<br>><br>>compacting the stack did help and things do<br>>seem to be settling down.<br>><br>>anyone else ever experience this?<br>><br>>thanks,<br>><br>>Erik Hansen<br>><br>>=====<br>>erik at<br>><br>><br>>	<br>>		<br>>__________________________________<br>>Do you Yahoo!?<br>>Vote for the stars of Yahoo!'s next ad campaign!<br>><br>>_______________________________________________<br>>use-revolution mailing list<br>>use-revolution at<br>><br>><br>>  <br>><br>_______________________________________________<br>use-revolution mailing list<br>use-revolution at<br><br>

Join Excite! -
The most personalized portal on the Web!

More information about the use-livecode mailing list