Using 1.4 I get different line numbers, calc_hole() is on line 240. Line 241 is not marked as executable, a bug. 242 is marked as executable (green). I set a breakpoint and push Calculate and it hits.
If you don't have green lines, the breakpoint will not hit. If you have green lines but they are off by the source lines, then you may be a victim of https://bugzilla.mozilla.org/show_bug.cgi?id=488730 If so, the workaround is to ensure you have no extra whitespace on any lines. It took me a long time to find this problem because my editor (eclipse) automatically cleans up the lines on save. The bug has been fixed for some future version of Firefox, TBD. If you have green lines and the breakpoint still won't hit, you could still be a victim of the whitespace bug: with enough whitespace offset and enough code the lines from one function can be offset into another. Then you may also break in a function you did not expect. Look around in the Script panel: if the green lines don't line up, its likely that cleaning up the whitespace will help. If none of this seems to apply, then your problem is not likely due to Firebug alone (because it works for me). So the next step would be to install Firebug in new Firefox profile and see if it works. If yes, then one other extension is likely an issue. If not, let's consider that case later... jjb On May 29, 2:43 pm, Captain Paralytic <[email protected]> wrote: > I now have the new version installed and it still doesn't work. > > OK, here is a test case: > > Go tohttp://www.osg-uk.com/swedej1/index.php?option=com_facileforms&Itemid=50 > In Firebug Scripts, search for "_hole" to find the function calc_hole > () on line 203. > I then put a break on line 204. > In the text boxes on the form put any positive number (e.g. 1) > Hit the Calculate Hole Size button. > > In my FireBug, the function just executes and the break is ignored. > When I click on the Breakpoints tab, I see the breakpoint labelled > "undefined" > > I will try to find an example of it not showing errors. > > On 29 May, 20:27, johnjbarton <[email protected]> wrote: > > > Ok let us know if you would like to get the problem fixed. All we > > need is for you to try Firebug 1.4 and if it fails, provide a test > > case. > > > jjb > > > On May 29, 11:38 am, Captain Paralytic <[email protected]> wrote: > > > > I have the same problem. I am using: > > > FF 3.0.10 > > > Firebug 1.3.3 > > > > I also have installed: > > > Firefox Showcase 0.9.5 > > > FirePHP 0.3 > > > Google Redesigned 0.3 > > > Measureit 0.3.8 > > > Web Developer 1.1.6 > > > > As well as breakpoints not working, I also note that Firebug is not > > > showing javascript errors unless I select "Break on All Errors" > > > > Going back to Firefox 2 to do my debugging (it wrks fine there using > > > Firebug 1.0.5) > > > > On May 29, 1:37 pm, Rob Campbell <[email protected]> wrote: > > > > > seconding johnjbarton's request to get a version number of Firebug > > > > that you're working with. > > > > > If you're using one of the 1.4 alphas, you may have to Reload the web > > > > page for the script and console to work properly. > > > > > On May 28, 6:40 pm, "[email protected]" <[email protected]> > > > > wrote: > > > > > > I'm trying to debug an extJS based JavaScript form in Firefox 3.0.8, > > > > > with Firebug, but none of my debugging statements are working. > > > > > console.log' produces the error console is not defined in the console. > > > > > The debugger` statement just doesn't work. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
