On Feb 11, 1:45 am, woomla <[email protected]> wrote:
> Hi,
>
> Although the debugger does a great job I have a feature request.
>
> Currently the debugger steps on the last line, with actual code, of a
> block even if that line is not executed. This makes debugging in the
> example below a bit harder to follow. In the example, the debugger
> always steps on line 5, even if line 3 is false. The only difference
> is that in that case line 5 is not executed, but you cannot tell by
> the debugger.
>
> Is it possible that the debugger skip line 5 if line 3 is false and
> goes to line 6 (or 7 or 1 in this case)?
While I appreciate your generous comments, I think this is just a bug.
However its not one that is simple to fix, we need to have new values
in the program counter map from Firefox.
Firebug supports single stepping by interrupting execution after every
step of the program counter (PC). Then it asks Firefox what line of
source the PC value maps to. If the line has not changed, it steps
again. When the line changes, it breaks into the UI for the user.
So if the PC -> line number map is incorrect, the break will be
incorrect. Firebug does not know anything about the structure of the
program.
If you post a small complete test case to our issues list I will
report it to bugzilla.mozilla.org.
jjb
>
> 1: for (key in obj)
> 2: {
> 3: if (obj.hasOwnProperty(key))
> 4: {
> 5: result += key + ',';
> 6: }
> 7: }
--
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.
