(my prev snipped out to save space)
On Oct 26, 2005, at 1:18 PM, J. Landman Gay wrote:
This sounds like the problem we have discussed before, where if
there is an error in a function or handler call and the breakpoint
is set in the calling handler, the debugger will simply run to the
end and/or exit. This is preferable to MetaCard's debugger
behavior, where the problem causes infinite, recursive error
messages and you have to force-quit.
I suspect there is a problem with the libdb_addToTable call. If you
comment out that line and you see normal debugging behavior, then
that's what is going on.
Ah, but that's the thing -- there *wasn't* a problem. (I know because
everything comes out right in later handlers.)
When I get a chance to try this again, I'll try to isolate the
behavior better.
coh
_______________________________________________
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
