The green lines are executable lines, that is lines with JavaScript that can be reached by the debugger when you set a breakpoint. I also saw earlier that Firebug didn't reliably mark them as green, though I made a few quick tests right now and in these tests it was always right. There are also some related issues <https://code.google.com/p/fbug/issues/list?can=2&q=executable+lines> reported. Unfortunately it allows you to set breakpoints at unreachable areas, e.g. within HTML or at empty lines within JavaScript, which should be automatically corrected, though that code doesn't seem to work correctly.
If you have a test case with reproducible steps where the executible lines are incorrectly set, you should create issues for it <https://code.google.com/p/fbug/issues/entry>. Sebastian On Sunday, March 1, 2015 at 6:16:41 AM UTC+1, San wrote: > > I still don't have a test-case that I can make public for the ongoing > problem with some breakpoints not working (in Firefox 36, with Firebug > 2.0.8, in both Mac and Win7). The issue for me is that in some cases > Firebug stops at the red "breakpoint" circle, but doesn't put the yellow > triangle in it, at which point all the debugger buttons are grayed out and > don't work. > > No test case, but I think I may have a clue as to what's happening. I got > this by comparing the behavior of the Firebug debugger with Chrome's > debugger on the same files and code lines. (BTW I'm finding Chrome's > debugger *much* more reliable, although overall I still prefer Firebug, > maybe just because I'm more used to it.) > > In Chrome I don't see any hints as to which code lines may be breakable; > it seems to let me put a breakpoint *anywhere*, and I only find out > whether it will work when I reload. This basically sucks. Helpfully, > Firebug *does* give such hints, by making the breakable line numbers > green. I now suspect that the problem may be that Firebug is making some > line numbers green that it shouldn't -- fooling me into thinking those > lines can take breakpoints, and letting me click to make a red circle > there. So the problem may not be so much "breakpoints failing" as "showing > too many bogus breakable lines." > > I hope this may help the developers fix this problem, although I don't > hold much hope frankly. > > BTW, can anybody explain WHY (in any debugger) some lines can take > breakpoints and some can't? Offhand I haven't noticed any pattern there but > I suspect there is one, something inherent to JavaScript itself rather than > any particular debugger. What is the logic there? Thanks. > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/642e3afc-3f9c-4837-a274-9f0e80f3362a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
