Hi Joe,
Short of universal execution controllers (which I'm not aware of), I would
recommend you do something like this:
First, identify where the problem is.
- comment out most of your code, just leaving some very basic stuff.
- save.
- run a test.
- uncomment a little code.
- save.
- do another test.
- repeat this cycle until you get a failure.
When you finally get a failure, you'll know it's associated with the code you
most recently uncommented.
Second, use one of the methods you now know from previous posts to interrupt the
endless loop when it happens.
HTH -
Phil Davis
[EMAIL PROTECTED] wrote:
In a message dated 2/3/07 3:57:24 PM, [EMAIL PROTECTED] writes:
Hi Everyone
Is there a way for me to stop a running script that’s caught in an endless
loop so I can fix my scripting error?
Joe
Orlando, Florida
I tried “AllowInterrupts” it didn’t allow me to break in, even when I put it
into the offending handler. The other suggestions assume I know in advance
which handler will cause a problem. Is there a universal solution I can apply at
startup to allow me to break a script?
Joe
Orlando, Florida
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
