1c7c0521f1
Previously, the stack property was set up in JS as read-only; but since it had a JS setter, writability was ignored and writing to stack was possible. This is no longer the case now that stack is either an actual data property, or is associated with C++ accessors. Explicitly set the property as writable to preserve old behavior. BUG=5245 R=yangguo@chromium.org Review-Url: https://codereview.chromium.org/2190313002 Cr-Commit-Position: refs/heads/master@{#38158}
25 lines
651 B
JavaScript
25 lines
651 B
JavaScript
// Copyright 2016 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
"use strict";
|
|
|
|
// After captureStackTrace.
|
|
|
|
var a = {};
|
|
Error.captureStackTrace(a, Error);
|
|
a.stack = 1; // Should not throw, stack should be writable.
|
|
|
|
// After the standard Error constructor.
|
|
|
|
var b = new Error();
|
|
b.stack = 1; // Should not throw, stack should be writable.
|
|
b.stack = 1; // Still writable.
|
|
|
|
// After read access to stack.
|
|
|
|
var c = new Error();
|
|
var old_stack = c.stack;
|
|
c.stack = 1; // Should not throw, stack should be writable.
|
|
c.stack = 1; // Still writable.
|