Bug 144577
| Summary: | Web Inspector: JS syntax errors are awkward to debug when "Pause on Uncaught Exceptions" is enabled | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brian Burg <burg> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | graouts, inspector-bugzilla-changes, jonowells, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Brian Burg
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/20800102>