117749 2013-06-18 12:39:24 -0700 Inline call frames fail to initialize unmodified argument slot correctly 2013-06-18 16:09:15 -0700 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 117602 InRadar P2 Normal --- 1 oliver webkit-unassigned fpizlo oliver oldest_to_newest 901479 0 oliver 2013-06-18 12:39:24 -0700 function g() { f(i) } function f() { arguments; doStuff(); } function doStuff() { throw f.arguments; } var h; for (var i = 0; i < 100; i++) { try { g() } catch (e) { if (!h) h = e; } } print(h[0]); or function g() { f(i) } function f() { arguments; doStuff(); } function doStuff() { throw f.arguments; } var h; for (var i = 0; i < 100; i++) { try { g() } catch (e) { if (i == 90) h = e; } } print(h[0]); 901481 1 oliver 2013-06-18 12:40:41 -0700 <rdar://problem/14192906> 901562 2 fpizlo 2013-06-18 15:43:29 -0700 Is this just a dupe of https://bugs.webkit.org/show_bug.cgi?id=117602? Isn't the problem that op_throw in the DFG ByteCodeParser doesn't flush captured variables correctly? 901572 3 oliver 2013-06-18 16:09:15 -0700 (In reply to comment #2) > Is this just a dupe of https://bugs.webkit.org/show_bug.cgi?id=117602? > > Isn't the problem that op_throw in the DFG ByteCodeParser doesn't flush captured variables correctly? Yeah I think so, i filed while i was originally trying to work out what was going wrong. *** This bug has been marked as a duplicate of bug 117602 ***