Hi Mark,
I guess I submitted BZ report #3086, on 8-26-2005. I think I've
upgraded to 2.6.1 since then. I originally isolated the problem in
2.5. It does seem to resemble bug 329, doesn't it?
Maybe Rev should consider putting up a "workaround page" for issues
like this, when workarounds are available, pending bug fixes. (A wiki
would serve the same purpose, of course. Maybe that's gonna happen.)
Cheers,
Tim
Tim,
I would like to know whether you have solved the problem you had
with debugging background scripts. If not, feel free to send you
stack to me. You can also add your (very good) analysis to bug 329
of the Bugzilla database.
In my view, the debugger should never just drop out of debug mode.
It should give some feedback to tell the user why it can't continue
debugging. If we can figure out what happened with your stack, maybe
RunRev can add some proper error handling in the deugger.
Best,
Mark
_______________________________________________
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
