21181 2008-09-27 14:59:07 -0700 Web Inspector: show actual argument values and function names for each frame in stack traces 2016-12-13 15:33:47 -0800 1 1 1 Unclassified WebKit Web Inspector 528+ (Nightly build) All All NEW InRadar P2 Normal --- 13646 1 timothy webkit-unassigned aroben inspector-bugzilla-changes jonowells jwalden+bwo keishi kmccullough laszlo.gombos webkit-bug-importer webkit.org yurys oldest_to_newest 93078 0 timothy 2008-09-27 14:59:07 -0700 We should show the arguments for each function in the stack. Similar to GDB's 'bt' command. 399460 1 webkit.org 2011-05-06 04:57:20 -0700 (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() 1055897 2 burg 2014-12-16 00:21:38 -0800 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, ...) 1056395 3 webkit-bug-importer 2014-12-17 11:20:32 -0800 <rdar://problem/19281453>