-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v8.x backport] deps: backport 9a23bdd from upstream V8 #22418
Conversation
f7e7a28
to
280f095
Compare
280f095
to
fad8bc7
Compare
@nodejs/v8 @nodejs/v8-update @nodejs/release PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please bump the patch level version in v8-version.h
as per the maintaining V8 guide:
@richardlau updated patch level in |
caf2708
to
308fb6e
Compare
The change LGTM, but the general policy is that we allow fixes to be released on Current first before back-porting to LTS. AFAICT, this has not been released on Current yet. |
Marked as blocked until #22338 lands or https://bugs.chromium.org/p/v8/issues/detail?id=7916 gets backported upstream. |
Original commit message: [Isolate] Fix Isolate::PrintCurrentStackTrace for interpreted frames Previously we were getting the code object from the stack, so printed incorrect position details for interpreted frames. BUG=v8:7916 Change-Id: I2f87584117d88b7db3f3b9bdbfe793c4d3e33fe9 Reviewed-on: https://chromium-review.googlesource.com/1126313 Reviewed-by: Toon Verwaest <[email protected]> Commit-Queue: Ross McIlroy <[email protected]> Cr-Commit-Position: refs/heads/master@{nodejs#54253} Refs: v8/v8@9a23bdd Fixes: nodejs#21988
308fb6e
to
94402b0
Compare
v8/v8@9a23bdd landed on master through #21983, which means we can move forward with this PR.
CI: https://ci.nodejs.org/job/node-test-pull-request/17404/ |
Original commit message: [Isolate] Fix Isolate::PrintCurrentStackTrace for interpreted frames Previously we were getting the code object from the stack, so printed incorrect position details for interpreted frames. BUG=v8:7916 Change-Id: I2f87584117d88b7db3f3b9bdbfe793c4d3e33fe9 Reviewed-on: https://chromium-review.googlesource.com/1126313 Reviewed-by: Toon Verwaest <[email protected]> Commit-Queue: Ross McIlroy <[email protected]> Cr-Commit-Position: refs/heads/master@{#54253} Refs: v8/v8@9a23bdd Fixes: #21988 PR-URL: #22418 Refs: #22338 Reviewed-By: Matheus Marchini <[email protected]> Reviewed-By: Ujjwal Sharma <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Landed in 9e2077a |
Original commit message:
Refs: v8/v8@9a23bdd
Refs: #22338
Fixes: #21988
Checklist
[x]
make -j4 test
(UNIX), orvcbuild test
(Windows) passes[x] commit message follows commit guidelines