[Webkit-unassigned] [Bug 63398] Poisoning of strict caller, arguments inappropriately poisoning "in"

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=63398





--- Comment #1 from Mark S. Miller <erights at gmail.com>  2011-06-26 06:42:48 PST ---
I'm using WebKit Nightly Version 5.0.5 (5533.21.1, r89741).


A further weirdness is that the TypeError that's thrown isn't caught by a one level try/catch.

try { 'caller' in function(){"use strict"} } catch (e) {}
TypeError: Cannot access caller property of a strict mode function


Further testing in the context of a larger system (look for "has(" in http://codereview.appspot.com/4603044/patch/8002/18002?column_width=100 ) indicates that there is some two level combination of try/catch/finally which can catch the TypeError in the out catch, even though it had skipped past both the inner catch and finally. However, I haven't isolated this yet into a standalone test case. This may be symptom of a distinct bug.

Without one of the finallys there, I also found that testing under the WebKit debigger caused WebKit as a whole to crash. I haven't yet isolated that either.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.