Manoj - A runtime callgraph is *exactly* what I need. This would help me get a quick handle on third party libs!
As a workaround, I ran the FB profiler while the bug appeared, and cut/ pasted into a spreadsheet. I then ran the FB profiler when the bug was not present, and pasted those results in the same spreadsheet. I matched the two lists and found a handful of invocations that were different. I found the bug inside one of the differences. A call graph would definitely provide a cleaner and more precise way to detect bugs! Best regards, Tom Agnew On Dec 1, 7:56 pm, Manoj <[EMAIL PROTECTED]> wrote: > The following is an enhancement I'm working on currently which may > address some of your needs: > > http://groups.google.com/group/firebug/browse_thread/thread/201d6ca29... > > Regards, > Manoj > > On Nov 30, 3:35 pm, Tom <[EMAIL PROTECTED]> wrote: > > > How can i produce a 'full trace' of a .js? > > > I'm trying to hack a very large library and would like to see a > > snapshot of all functions that are called during an execution. Adding > > individual breakpoints or log messages is very time consuming. > > > I'd like to generate a list of all functions invoked, so i can peruse > > and begin a more targeted debugging session. > > > Is this possible in Firebug? > > > Best regards, > > Tom Agnew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
