I think I finally get what is going on - Firebug seems to detect all executable lines correctly, but for some reason, it repeats the contents of a .js file (any/all .js files, in my case) in the Script viewer three times? For instance, I notice:
213 return myobject; 214} // end of file1.js 215// start of file1.js <=== again beginning?! 216 And of course, from that point on, all lines are non-executable. So I guess, there is no real bug execution-wise, only display/UI-wise :) Cheers! On Dec 27, 7:33 pm, sdaau <[email protected]> wrote: > Ah well... tried to do > > * Uninstall Firebug > * Clean Firefox extension > cache:http://kb.mozillazine.org/Firefox_:_FAQs_:_Uninstall_Extensions#Corru... > * Reinstall Firebug 1.4.5 > > Still same problem - lines in .js files are not marked as executable > after about a 3rd of the total ammount of lines in a file. > > Then I found > > Breakpoints not being triggered in Firebug 1.4.5 - Firebug | Google > Groups > -http://groups.google.com/group/firebug/browse_thread/thread/0c7fb2d33... > > And installed Firebug 1.5b8 - still the same behavior... > > Well, hope I can get some pointers on this .. > > Cheers! > > On Dec 27, 6:30 pm, sdaau <[email protected]> wrote: > > > OOps, seems I was a bit too soon on that... after about an hour of > > normal operation, now Firebug is back to giving undefined breakpoints. > > I noticed, however, that those lines in code which are possible to > > have a breakpoint assigned, are shown with green line numbers - there > > proper breakpoins can be set. > > > The funny thing is that in most files, the beginning has green lines - > > and then at a certain point it stops, and all below is treated as non- > > breakable code... Even funnier is that it seems to follow a pattern - > > in my example: > > > file1.js is 996 lines; last breakable is line 330 > > file2.js is 1860 lines; last breakable is line 616 > > file3.js is 702 lines; last breakable is line 232 > > > That is, it seems that the process (determining whether a line is > > breakable or not) starts reading a .js file, comes up to about a third > > of its length, and then it quits. Maybe has something to do with a > > memory leak? > > > Cheers! > > > On Dec 27, 5:26 pm, sdaau <[email protected]> wrote: > > > > Hi, > > > > I'd just like to report that I was using Firebug with breakpoints in a > > > project, and it all was working fine, until I installed the FirePHP > > > plugin. At that point, when setting breakpoints in some points in > > > code, their function would show up as "undefined", and they would not > > > be honored. After disabling FirePHP, all seems to be back to normal. > > > > FirePHP 0.3.1 > > > Firebug 1.4.5 > > > Firefox 3.5.6 Ubuntu 9.04 Jaunty > > > > Cheers! > > -- 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.
