[Webkit-unassigned] [Bug 144577] New: Web Inspector: JS syntax errors are awkward to debug when "Pause on Uncaught Exceptions" is enabled
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon May 4 09:06:14 PDT 2015
https://bugs.webkit.org/show_bug.cgi?id=144577
Bug ID: 144577
Summary: Web Inspector: JS syntax errors are awkward to debug
when "Pause on Uncaught Exceptions" is enabled
Classification: Unclassified
Product: WebKit
Version: 528+ (Nightly build)
Hardware: All
OS: All
Status: NEW
Severity: Normal
Priority: P2
Component: Web Inspector
Assignee: webkit-unassigned at lists.webkit.org
Reporter: burg at cs.washington.edu
CC: graouts at webkit.org, joepeck at webkit.org,
jonowells at apple.com, mattbaker at apple.com,
nvasilyev at apple.com, timothy at apple.com,
webkit-bug-importer at group.apple.com
Suppose you have some Foo class that consists of invalid JS. When you try to instantiate a Foo instance, JSC will complain that Foo doesn't exist, because it was never defined due to the syntax erorr.
If you have Pause on Uncaught Exceptions enabled, what happens is that it will pause on the constructor callsite without showing the parse error in the sidebar. Only once you continue will the actual error show up in the sidebar. I'm not sure if it's stuck in a nested runloop or what the cause is, but it makes debugging a parse error hard.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150504/6b0bd484/attachment.html>
More information about the webkit-unassigned
mailing list