Bug 144577 - Web Inspector: JS syntax errors are awkward to debug when "Pause on Uncaught Exceptions" is enabled
Summary: Web Inspector: JS syntax errors are awkward to debug when "Pause on Uncaught ...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2015-05-04 09:06 PDT by Brian Burg
Modified: 2016-12-13 15:33 PST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Burg 2015-05-04 09:06:14 PDT
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.
Comment 1 Radar WebKit Bug Importer 2015-05-04 09:06:58 PDT
<rdar://problem/20800102>