I run into this quite frequently. The workaround for me is to manually
put a breakpoint (the dot in the debugger) on a line after the thing
that causes the runaway. When it emerges from the function that causes
it to forget that it is in debug, it hits the one I manually added and
goes back into debug.
Kee Nethery
On Sep 27, 2008, at 10:21 PM, Len Morgan wrote:
I'm trying to debug the following:
...
breakpoint
put URL myURL into tTextOfURL
put "I made it"
It seems to be stopping ok at the breakpoint but when I execute the
next line (the put URL...), it skips to end of the handler.
Actually, to the next line of the handler that called this one.
Is there some issue with breakpoints and blocking handlers that I'm
not aware of?
Thanks!
len morgan
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
-------------------------------------------------
I check email roughly 2 to 3 times per business day.
Kagi main office: +1 (510) 550-1336
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
