Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(115)

Issue 13150003: Stack trace API: poison stack frames below the first strict mode frame. (Closed)

Created:
7 years, 9 months ago by Yang
Modified:
7 years, 9 months ago
Reviewers:
rossberg
CC:
v8-dev
Visibility:
Public.

Description

Stack trace API: poison stack frames below the first strict mode frame. Function and receiver objects are not accessible for poisoned frames. R=rossberg@chromium.org BUG=v8:2564 Committed: https://code.google.com/p/v8/source/detail?r=14085

Patch Set 1 #

Total comments: 8
Unified diffs Side-by-side diffs Delta from patch set Stats (+164 lines, -50 lines) Patch
M src/isolate.cc View 3 chunks +16 lines, -1 line 0 comments Download
M src/messages.js View 6 chunks +56 lines, -49 lines 4 comments Download
A test/mjsunit/regress/regress-2564.js View 1 chunk +92 lines, -0 lines 4 comments Download

Messages

Total messages: 4 (0 generated)
Yang
7 years, 9 months ago (2013-03-28 09:44:53 UTC) #1
rossberg
LGTM with comments https://codereview.chromium.org/13150003/diff/1/src/messages.js File src/messages.js (right): https://codereview.chromium.org/13150003/diff/1/src/messages.js#newcode755 src/messages.js:755: var CallSiteReceiverKey = %CreateSymbol("receiver"); Nit: do ...
7 years, 9 months ago (2013-03-28 10:04:33 UTC) #2
Yang
Committed patchset #1 manually as r14085 (presubmit successful).
7 years, 9 months ago (2013-03-28 10:40:16 UTC) #3
Yang
7 years, 9 months ago (2013-03-28 10:55:03 UTC) #4
Message was sent while issue was closed.
https://codereview.chromium.org/13150003/diff/1/test/mjsunit/regress/regress-...
File test/mjsunit/regress/regress-2564.js (right):

https://codereview.chromium.org/13150003/diff/1/test/mjsunit/regress/regress-...
test/mjsunit/regress/regress-2564.js:34: Error.prepareStackTrace = undefined; 
// Prevent recursion.
On 2013/03/28 10:04:33, rossberg wrote:
> Not sure I understand why this is necessary here. Should the below throw?

No, but if it does, i.e. assertion failure, the error message looks more sane.

https://codereview.chromium.org/13150003/diff/1/test/mjsunit/regress/regress-...
test/mjsunit/regress/regress-2564.js:59: var o = [ function f0() { throw new
Error(); },
On 2013/03/28 10:04:33, rossberg wrote:
> Maybe add a third test where the throwing function itself is strict.

Done.

Powered by Google App Engine
This is Rietveld 408576698