X Tutup
Skip to content

report: handle on-fatalerror better#32207

Closed
HarshithaKP wants to merge 4 commits intonodejs:masterfrom
HarshithaKP:diagnostic_report_fatal_error
Closed

report: handle on-fatalerror better#32207
HarshithaKP wants to merge 4 commits intonodejs:masterfrom
HarshithaKP:diagnostic_report_fatal_error

Conversation

@HarshithaKP
Copy link
Copy Markdown
Member

--report-on-fatalerror was not honored properly, as there was no
way to check the value which was stored in the Environment pointer
which can be inaccessible under certain fatal error situations.

Move the flag out of Environment pointer so that this is doable.

Co-authored-by: Shobhit Chittora schittora@paypal.com

Fixes: #31576
Refs: #29881

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Loading
Sign up for free to 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++. lib / src Issues and PRs related to general changes in the lib or src directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Diagnostic report on fatal error does not respect settings

7 participants

X Tutup