Uh, no, totally new to me... that would (somewhat) help show/debug yui- compressed (no line endings) code? I'm not using eval.
Any description on this? Hmmm, I just googled around and the only thing I found was related to eval... On Jun 23, 1:55 pm, johnjbarton <[email protected]> wrote: > By the way, do you know about //@ sourceURL=<url> for eval()? > If you are sending down 65kloc, (ok 2 x 32kloc), you can write a > little code to unpack it on the browser side and post pend the string > with the file name. Firebug should put the source files in the Script > panel for you then. > > jjb > > On Jun 22, 7:33 pm, Steven Roussey <[email protected]> wrote: > > > I'm always getting annoyed with the stack trace of javascript error > > showing me random lines (and highlighting them, even if they are > > comments). So I used IE8 to get the real stack trace. The line in > > question was 67758. In Firebug it said 2222. Guess what 67758 - 2222 > > is? 65536 (2^16). So there is an overflow error, likely in Firefox. > > > From the look of things, firebug is applying the green "these are > > breakpoint-able lines of code" for lines 65536+ back onto the file > > again, though where/when I have yet to identify. > > > Moral of the story, when developing, be sure to break up all your JS > > files. > > > Win7 x64 > > Fx 3.0.11 & Fx 3.5RC > > Fbug 1.5X5 (plus many many earlier) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
