Skip to content

Conversation

@addaleax
Copy link
Member

Fixes: #33578

/cc @devsnek Since I can’t reproduce, I didn’t feel 100 % comfortable to add a test here. If you can put your repro into the form of a regression test, feel free to push to this branch.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-botnodejs-github-bot added the c++ Issues and PRs that require attention from people who are familiar with C++. label May 29, 2020
@BridgeARBridgeARforce-pushed the master branch 2 times, most recently from 8ae28ff to 2935f72CompareMay 31, 2020 12:18
@addaleaxaddaleax requested a review from devsnekJune 5, 2020 19:29
@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Jun 5, 2020

@addaleaxaddaleax added the review wanted PRs that need reviews. label Jun 6, 2020
@addaleaxaddaleax requested review from Trott and jasnellJune 8, 2020 18:42
@addaleax
Copy link
MemberAuthor

Landed in 4678e44

@addaleaxaddaleax closed this Jun 9, 2020
addaleax added a commit that referenced this pull request Jun 9, 2020
@addaleaxaddaleax deleted the node-errors-sourceline-bounds branch June 9, 2020 13:23
@MylesBorins
Copy link
Contributor

Hey @addaleax this doesn't land cleanly on 14.x, it appears to make changes to source text that hasn't landed yet as part of #33491.

Would you up to making a backport

targos pushed a commit that referenced this pull request May 1, 2021
@danielleadamsdanielleadams mentioned this pull request May 3, 2021
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++Issues and PRs that require attention from people who are familiar with C++.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SIGSEGV in node::GetErrorSource

5 participants

@addaleax@nodejs-github-bot@MylesBorins@Trott@targos