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.
