[Webkit-unassigned] [Bug 128776] Web Inspector: JSContext inspection should report exceptions in the console

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 14 19:41:01 PST 2014


--- Comment #2 from Joseph Pecoraro <joepeck at webkit.org>  2014-02-14 19:38:15 PST ---
Created an attachment (id=224275)
 --> (https://bugs.webkit.org/attachment.cgi?id=224275&action=review)
[IMAGE] Example 1

As a user of the JSC APIs the exception will often (always?) be a result of an explicit API Call. The only cases I can think of where this is not the case is evaluating scripts in Web Inspector's console. There are no asynchronous JavaScript APIs available at this time (setTimeout, Promises, etc.)

If an exception is the result of an API call, it will be extremely useful to have not only the JavaScript exception stack but also the native call stack above the JSC API entry point. Otherwise the developer is left with little more then the idea that an exception happened without any information about when or where. See attached screenshots.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list