Bug 145522
| Summary: | Track exception values and stack trace together in an Exception object | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mark Lam <mark.lam> |
| Component: | JavaScriptCore | Assignee: | Mark Lam <mark.lam> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | benjamin, fpizlo, ggaren, keith_miller, mmirman, msaboff, saam |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 145525 | ||
Mark Lam
We currently track exceptions as 2 values in the VM: m_exception (the thrown JSValue) and m_exceptionStack (a capture of the stack trace at the time of throw). This increases the complexity of having to keep the 2 values in sync every time we throw, clear, stash away, and restore exceptions. We should introduce an Exception object to better encapsulate all the state pertaining to an exception throwing event.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Lam
After reviewing the needed changes, there's not enough difference between the patch for this bug and the fix for bug 145525 (which this bug is intended to build towards). So, I'll just roll this bug into 145525 and implement the fix there.
*** This bug has been marked as a duplicate of bug 145525 ***