Before, this could lead to confusion due to JS_IsExceptionPending usage and the like. Now it will lead to odd failure due to immediate rethrow on js_Interpret reentry (e.g., from eval). See bug 341821. ECMA-262 Edition 3 12.14 semantics for the second production are clear. We need to save the result of evaluating the try block while evaluating the finally, and propagate that result if the finally completes normally (not abruptly, e.g. by throwing or returning). /be
Created attachment 230825 [details] [diff] [review] fix Shaver, it would be great if you could give this a look too. /be
Comment on attachment 230825 [details] [diff] [review] fix sr=shaver
Attachment #230825 - Flags: superreview?(shaver) → superreview+
Fixed on trunk. /be
Status: ASSIGNED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
Attachment #230825 - Flags: approval1.8.1?
Comment on attachment 230825 [details] [diff] [review] fix a=mconnor on behalf of drivers for 1.8 branch
Attachment #230825 - Flags: approval1.8.1? → approval1.8.1+
You need to log in before you can comment on or make changes to this bug.