Revolution debugger issues

[Wil Dijkstra]

Although this quite probably nothing has to do with your problems, the MC
debugger always runs into problems if you set the breakpoint after you
changed the lineDelimiter to something else than cr, e.g.
set linedelimiter to tab
Nevertheless, you may check if you happen to change the linedelimiter
somewhere before the breakpoint. I don't know if this happens in the rev
debugger too (I'm an MC addict, using rev only for its better
documentation).

Wil Dijkstra



On 8/4/05 6:41 AM, "Scott Rossi" <scott at tactilemedia.com> wrote:

> Recently, J. Landman Gay  wrote:
> 
>> I'm writing to the MC list because I don't want to start a flame fest on
>> the main Rev list. Is anyone here using the Revolution debugger? There
>> is a problem with it that has had me going around the bend for the last
>> week and I'd like some help nailing it down so I can Bugzilla it.
> 
> Jacque:
> 
> I can't answer your question directly, however, one of the things you wrote
> struck a chord:
> 
>> Because I can't debug it, I can't figure out where the problem is.
> 
> You may recall, I wrote to Rev Support a few weeks ago vaguely describing a
> problem where garbage characters were intermittently winding up in global
> variables (that would otherwise evaluate correctly in the message box and
> simple scripts).  This did not involve the debugger specifically, but as in
> your case, it was something that took me days if not weeks to track down.
> And I still have no explanation for why it happens.
> 
> 
>> I accidentally did the above and instead of throwing an error,
>> myHandler2 ran, but var1 contained "123,abc" and var2 was empty. Because
>> breakpoints did not stop script execution and because the variable
>> watcher had no values, it took me days to find the problem.
> 
> This may be completely unrelated but, are you sure the problem only occurs
> when using the debugger?  If you run the scripts repeatedly, do the script
> problems occur at all intermittently even when not using the debugger?  If
> so, this sounds like the variable trouble I was having, and this occurred in
> MC, not Rev.  In my case, the only way I could work around it was to compare
> the value of the variable against something expected (in my case it was an
> object reference) and exit the handler if the value was unexpected.  I'm
> sorry I can't offer more help.  I would very much like to know if you (or
> others) uncover anything regarding this mystery.
> 
> Regards,
> 
> Scott Rossi
> Creative Director
> Tactile Media, Multimedia & Design
> -----
> E: scott at tactilemedia.com
> W: http://www.tactilemedia.com
> 
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard