Bug 21181
| Summary: | Web Inspector: show actual argument values and function names for each frame in stack traces | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Timothy Hatcher <timothy> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | aroben, inspector-bugzilla-changes, jonowells, jwalden+bwo, keishi, kmccullough, laszlo.gombos, webkit-bug-importer, webkit.org, yurys |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 13646 | ||
| Bug Blocks: | |||
Timothy Hatcher
We should show the arguments for each function in the stack. Similar to GDB's 'bt' command.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Xavier Morel
(In reply to comment #0)
> We should show the arguments for each function in the stack. Similar to GDB's 'bt' command.
Or Firebug's own implementation, which:
* Shows the function name (even for many anonymous functions, it infers the name from a container property I'd guess), this is mostly 19229
* Links the function name to the function itself (not just the file:line note)
* Hyperlinks all complex (object) arguments so that they can be inspected on their own
This results in a much nicer console.trace()
Brian Burg
See also: Theseus (http://www.joelbrandt.org/publications/lieber_chi2014_always-on_programming_visualizations.pdf)
Clearly this will be slow, so it should only be done by default for exceptional or opt-in cases (exceptions, console.error, console.trace, ...)
Radar WebKit Bug Importer
<rdar://problem/19281453>