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?
I've seen this as well but I've not looked into it. I'd guess that the
single step URL is broken.
The way single stepping works is this: create an identifier for the
current line, from the URL and line number concatenated into a string.
Then hook "interrupt" handler, so every step calls back to Firebug.
Go. When the call back comes, compare the current line ID to the
previous one. If it changed, break. Else Go.
Since this all works for Firebug, the likely problem is the URL.
Firebug suppresses chrome URLs; Chromebug requires them.
The way to verify this is to open Chromebug > Trace > Options (panel
tab mini menu) > FBS_STEP then try single stepping. You should get a
stream of info about stepping.
>
> I don't know if it's related or not, but the browser can be interacted
> with while javascript execution is stopped at a break point. I'm not
> sure how that's possible, but it occurs.
That is by design. Firebug disables Javascript on the nsIDOMWindow it
is debugging, since other wise it cannot debug it.
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
-~----------~----~----~----~------~----~------~--~---
