On Aug 23, 9:28 pm, Chris <[email protected]> wrote: > I have had to upgrade to Firebug 1.8 from 1.7 because I now have FF6 > (OSX Lion). Since doing so, the script panel in FB shows a truncated > source for my JSP pages. If I do a view source from within FF it shows > everything. External JS files appear to be ok, just not the JSP page > they are loaded from. I never saw this in FB 1.7. We have one online test case related to this problem here: http://getfirebug.com/tests/content/branches/1.9/script/1425/issue1425.html Does this test works for you?
> It doesn't always truncate at the same place either. Is there a way I > can debug the debugger to find out where it is crapping out? The best way is currently FBTrace - Firebug Tracing Console. Install from here: http://getfirebug.com/releases/fbtrace/1.8/ See some docs here: http://getfirebug.com/wiki/index.php/FBTrace To display related logs you can check following options: ERRORS - general errors CACHE - Firebug maintain internal cache for JS source (perhaps the cache doesn't store everything?) SOURCEFILES - related to debugger and source cache You could also utilize FBTrace's command line (Tools->Command line) and inspect the internal cache to see what is actually inside. Evaluate on the command line Firebug.currentContext.sourceCache.cache; A log should be created, expand it and pick the "Object" tab. The 'currentContext' represents the currently selected tab in the browser window. Honza -- 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.
