J. Landman Gay wrote:
Often it will step
though a couple lines of code then drop to the bottom of the handler.
You can set debug checkpoints which do not trigger the debugger at all.
This one is a known, and intentional, escape procedure. It happens when
there is a bug in a script that is called from your debugging script,
such as one in a library or backscript. If there is a bug in there, the
engine will go into an infinite loop (which is what happens in the MC
IDE, and you have to force-quit.)
Please send details to either me or the MC list, and I'll address it
ASAP. I don't use the debugger much myself, but cleaning it up and
enhancing it might get me to do so. :)
...
In my case, one of the bugs was in libURL. Every time I tried to debug
my downloading scripts, I got the skipped handler business. I was
finally able to track it down by setting breakpoints in libURL itself --
at which point Dave Cragg immediately fixed the problem.
libURL has probably the lowest bug density of any substantial Transcript
work I've seen. Amazing, admirable, and inspiring effort, Dave.
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.com
_______________________________________________
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
