Skip to content

[v8.x backport] deps: backport 9a23bdd from upstream V8 - #22418

Closed
Drieger wants to merge 1 commit into
nodejs:v8.x-stagingfrom
Drieger:backport-22338-to-v8.x
Closed

[v8.x backport] deps: backport 9a23bdd from upstream V8#22418
Drieger wants to merge 1 commit into
nodejs:v8.x-stagingfrom
Drieger:backport-22338-to-v8.x

Conversation

@Drieger

Copy link
Copy Markdown
Contributor

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 <verwaest@chromium.org>
Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54253}

Refs: v8/v8@9a23bdd
Refs: #22338
Fixes: #21988

Checklist

[x] make -j4 test (UNIX), or vcbuild test (Windows) passes
[x] commit message follows commit guidelines

@nodejs-github-botnodejs-github-bot added v8 engine Issues and PRs related to the V8 dependency. v8.x labels Aug 20, 2018
@Drieger
Driegerforce-pushed the backport-22338-to-v8.x branch from f7e7a28 to 280f095CompareAugust 21, 2018 11:02
@DriegerDrieger changed the title [v8.x backport] deps: cherry-pick 9a23bdd from upstream V8[v8.x backport] deps: backport 9a23bdd from upstream V8Aug 21, 2018
@Drieger
Driegerforce-pushed the backport-22338-to-v8.x branch from 280f095 to fad8bc7CompareAugust 21, 2018 11:39
@mmarchini

Copy link
Copy Markdown
Contributor

@nodejs/v8 @nodejs/v8-update @nodejs/release PTAL

@ryzokukenryzokuken left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@richardlaurichardlau left a comment

Copy link
Copy Markdown
Member

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:

https://github.com/nodejs/node/blob/master/doc/guides/maintaining-V8.md#backporting-to-abandoned-branches

@Drieger

Copy link
Copy Markdown
ContributorAuthor

@richardlau updated patch level in v8-version.h

@Drieger
Driegerforce-pushed the backport-22338-to-v8.x branch from caf2708 to 308fb6eCompareAugust 21, 2018 16:55
@ofrobots

Copy link
Copy Markdown
Contributor

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.

@mmarchinimmarchini added the blocked PRs that are blocked by other issues or PRs. label Aug 22, 2018
@mmarchini

Copy link
Copy Markdown
Contributor

Marked as blocked until #22338 lands or https://bugs.chromium.org/p/v8/issues/detail?id=7916 gets backported upstream.

@DriegerDrieger closed this Sep 10, 2018
@DriegerDrieger reopened this Sep 10, 2018
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 <verwaest@chromium.org>
Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
Cr-Commit-Position: refs/heads/master@{nodejs#54253}
Refs: v8/v8@9a23bddFixes: nodejs#21988
@Drieger
Driegerforce-pushed the backport-22338-to-v8.x branch from 308fb6e to 94402b0CompareSeptember 10, 2018 13:34
@mmarchinimmarchini removed the blocked PRs that are blocked by other issues or PRs. label Sep 13, 2018
BethGriggs pushed a commit that referenced this pull request Oct 2, 2018
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 <verwaest@chromium.org>
Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54253}
Refs: v8/v8@9a23bddFixes: #21988
PR-URL: #22418
Refs: #22338
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
Reviewed-By: Ujjwal Sharma <usharma1998@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
@BethGriggs

Copy link
Copy Markdown
Member

Landed in 9e2077a

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v8 engineIssues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@Drieger@mmarchini@ofrobots@BethGriggs@richardlau@ryzokuken@nodejs-github-bot