Skip to content
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

deps: cherry-pick de5aaad from V8's upstream #8099

Closed
wants to merge 1 commit into from

Conversation

targos
Copy link
Member

@targos targos commented Aug 14, 2016

Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

V8

Description of change

Original commit message:

[Debugger] Fix StepNext over function with caught exception

Without CL debugger on StepNext adds breakpoint to function where
throw instruction is located. In case of StepNext we will skip pause
in this function because StepNext shouldn't break in a deeper frame.

BUG=chromium:604495
R=yangguo@chromium.org
LOG=N

Review URL: https://codereview.chromium.org/1894263002

Cr-Commit-Position: refs/heads/master@{#35627}

Fixes: #7219

cc @nodejs/v8

@targos targos added the v8 engine Issues and PRs related to the V8 dependency. label Aug 14, 2016
Original commit message:

    [Debugger] Fix StepNext over function with caught exception

    Without CL debugger on StepNext adds breakpoint to function where
    throw instruction is located. In case of StepNext we will skip pause
    in this function because StepNext shouldn't break in a deeper frame.

    BUG=chromium:604495
    R=yangguo@chromium.org
    LOG=N

    Review URL: https://codereview.chromium.org/1894263002

    Cr-Commit-Position: refs/heads/master@{nodejs#35627}

Fixes: nodejs#7219
@targos
Copy link
Member Author

targos commented Aug 14, 2016

@fhinkel
Copy link
Member

fhinkel commented Aug 14, 2016

LGTM

@bnoordhuis
Copy link
Member

LGTM. Unrelated CI failures, AFAICT.

targos added a commit that referenced this pull request Aug 17, 2016
Original commit message:

    [Debugger] Fix StepNext over function with caught exception

    Without CL debugger on StepNext adds breakpoint to function where
    throw instruction is located. In case of StepNext we will skip pause
    in this function because StepNext shouldn't break in a deeper frame.

    BUG=chromium:604495
    R=yangguo@chromium.org
    LOG=N

    Review URL: https://codereview.chromium.org/1894263002

    Cr-Commit-Position: refs/heads/master@{#35627}

Fixes: #7219
PR-URL: #8099
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
@targos
Copy link
Member Author

targos commented Aug 17, 2016

Thanks. landed in a1d3a8d

@ofrobots this can be added to your backport PR to v6.x.

@targos targos closed this Aug 17, 2016
@targos targos deleted the fix-7219 branch August 17, 2016 07:43
@ofrobots ofrobots mentioned this pull request Aug 17, 2016
2 tasks
@ofrobots
Copy link
Contributor

Added to #8054.

@evanlucas
Copy link
Contributor

Added don't land on v6.x since it will added in #8054

ofrobots pushed a commit to ofrobots/node that referenced this pull request Aug 25, 2016
Original commit message:

    [Debugger] Fix StepNext over function with caught exception

    Without CL debugger on StepNext adds breakpoint to function where
    throw instruction is located. In case of StepNext we will skip pause
    in this function because StepNext shouldn't break in a deeper frame.

    BUG=chromium:604495
    R=yangguo@chromium.org
    LOG=N

    Review URL: https://codereview.chromium.org/1894263002

    Cr-Commit-Position: refs/heads/master@{nodejs#35627}

Fixes: nodejs#7219
PR-URL: nodejs#8099
Reviewed-By: bnoordhuis - Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants