I'm working on a quite complex javascript system, and Firebug is
always a lifesaver when debugging it.
Using 1.6X.0b1, after a while, it becomes impossible to add or remove
breakpoints. When I click on them, nothing happens. The only way to get
them working again is usually to restart Firefox. Sometimes reloading
the page works, but not always. The weird thing is, after reloading the
page, there is new breakpoints at weird places, as if Firebug had become
out of sync between the visuals and the internal line numbers (I'm
making something up here that seems to make sense but may be completely
wrong), so when I click on one spot Firebug adds internally a breakpoint
somewhere else.
Unfortunately, as in most of such bugs, repro steps are hard to get.
This happens most of the time after line-stepping over a breakpoint put
in event handling code.
What should I look for in Tracing to help for a fix to be found?
Regards
Nicolas Hatier
--
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.
