[Webkit-unassigned] [Bug 145525] New: finally blocks should not set the exception stack trace when re-throwing the exception.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jun 1 14:01:07 PDT 2015
https://bugs.webkit.org/show_bug.cgi?id=145525
Bug ID: 145525
Summary: finally blocks should not set the exception stack
trace when re-throwing the exception.
Classification: Unclassified
Product: WebKit
Version: 528+ (Nightly build)
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: JavaScriptCore
Assignee: webkit-unassigned at lists.webkit.org
Reporter: mark.lam at apple.com
Finally blocks are implemented as a Catch block with an op_throw at its end to re-throw the exception. Currently, this throw in the finally block is no different than the throw that originated the exception. As a result, the exception stack trace is now set to the re-throw location in the finally block. This results in the Inspector reporting the wrong throw point for the exception.
--
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/20150601/e62de312/attachment.html>
More information about the webkit-unassigned
mailing list