Bug 22608 - Add a test to verify line numbers in uncaught exceptions
Summary: Add a test to verify line numbers in uncaught exceptions
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Pam Greene (IRC:pamg)
Depends on:
Reported: 2008-12-02 16:09 PST by Pam Greene (IRC:pamg)
Modified: 2008-12-05 16:02 PST (History)
0 users

See Also:

New test + result (1.78 KB, patch)
2008-12-02 16:57 PST, Pam Greene (IRC:pamg)
darin: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Pam Greene (IRC:pamg) 2008-12-02 16:09:12 PST
Another test.
Comment 1 Pam Greene (IRC:pamg) 2008-12-02 16:47:21 PST
After examining the existing tests, I note that the difference here is that it's specifically an uncaught exception, so there's no Exception object.  The other fast/js/exception* tests are examining the properties of the Exception produced.
Comment 2 Pam Greene (IRC:pamg) 2008-12-02 16:57:23 PST
Created attachment 25692 [details]
New test + result

This test is not suited to the JS wrapper, because the uncaught exception halts parsing.

The test also currently doesn't produce the right output, instead saying the exception was thrown on line 0. Unfortunately, there's no good way to mark it as an expected failure (no way to have FAIL come up in the expected results). All in all, not an ideal test, but I don't know of a better way to check what it's looking at.

The line-number error looks like bug 5206.
Comment 3 Darin Adler 2008-12-04 09:23:27 PST
Comment on attachment 25692 [details]
New test + result

No harm in having this test checked in.

Comment 4 Pam Greene (IRC:pamg) 2008-12-05 16:02:31 PST
Landed r39054