On May 6, 5:35 am, Morac <[email protected]> wrote:
> I'm using the Chromebug 1.5 svn branch with Firebug 1.4X.0a25.
> Everything seems to work fine except that if I stop execution at a
> breakpoint and try to step through the code (step in, over or out) it
> just resumes execution. The only way to "step" through code is to put
> in a break point on every line. Any idea why that is?
>
Fixed at R2844 on branches/firebug1.4. Chromebug needs the frame
(jsdIStackFrame) to assign the execution point to a context it is
tracking. Firebug settles for a 'window', since that is all Firebug
can work with. If the execution point lands outside of a window,
Firebug just ignores it. Chromebug has the ambition to debug
everything, so it wants to try harder. For that it needs the frame.
Sorry for the delay and thanks for your interest,
jjb
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
