I've been seeing the same thing since 1.6.19a I think. It'll break at the correct place but will "script location" will be a different file. I've just been making sure to reselect the current file in the script location dropdown which has been a slight inconvenience. It doesn't happen all the time (maybe 50% or so) and haven't been able to reproduce consistently.
On Sep 1, 6:17 pm, Nicolas Hatier <[email protected]> wrote: > I confirm what "ed" said, sometimes, when a breakpoint is reached in a > js file, while the script panel displays the js file content, the > "script location menu" lists the main HTML file as the currently > selected script. > > When I add a breakpoint, it is added to the corresponding line in the > main HTML file. > > I'm still working on a test case or a tracing capture, but, given these > new findings, I'm not sure BP tracing will give me the wanted results. > > Nicolas > > On 2010-08-30 11:41, John J Barton wrote: > > > > > On Aug 29, 2:12 pm, ed<[email protected]> wrote: > >> I've been seeing this in the past few 1.6 versions also. When it > >> happens, I notice that when I click in the margin to set the > >> breakpoint, the source file listed is the main html file name, and not > >> the script file, so the line number us usually invalid and a > >> breakpoint isn't set. > > All I need to fix this is a test case. > > jjb > > >> On Aug 29, 12:51 am, Nicolas Hatier<[email protected]> wrote: > > >>> 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.
