Bug 161508 - GlobalFuncProtoSetterFunctor sometimes fails to get caller frame
Summary: GlobalFuncProtoSetterFunctor sometimes fails to get caller frame
Status: RESOLVED DUPLICATE of bug 161455
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Chris Dumez
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-01 14:03 PDT by Chris Dumez
Modified: 2016-09-02 17:00 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dumez 2016-09-01 14:03:58 PDT 
GlobalFuncProtoSetterFunctor sometimes fails to get caller frame.

It skips the first frame, then there is no more frame so m_allowsAccess does not get initialized.

Happens during:
JSTests/stress/proxy-json-path.js

Found after landing patch for Bug 161455 because it started throwing a TypeError when trying to set __proto__ instead of merely ignoring the call.
Comment 1 Mark Lam 2016-09-01 15:24:22 PDT 
Sending back to Chris since he'll be looking into this.
Comment 2 Chris Dumez 2016-09-02 11:42:37 PDT 
Dropped this code in Bug 161455.

*** This bug has been marked as a duplicate of bug 161455 ***