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

report: reuse triggerReport() for exceptions and signals #26386

Merged
merged 5 commits into from
Mar 4, 2019

Conversation

cjihrig
Copy link
Contributor

@cjihrig cjihrig commented Mar 2, 2019

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

@nodejs-github-bot nodejs-github-bot added 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. labels Mar 2, 2019
@richardlau richardlau added the report Issues and PRs related to process.report. label Mar 2, 2019
cjihrig added 5 commits March 3, 2019 19:25
This commit uses the triggerReport() binding to handle
uncaught exceptions and removes the custom onUncaughtException
function.

PR-URL: nodejs#26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
PR-URL: nodejs#26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
This commit uses the triggerReport() binding to handle
signals and removes the custom onUserSignal() function.

PR-URL: nodejs#26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
PR-URL: nodejs#26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
trigger more accurately describes the use of the field.
Previously, location was just the name of the C++ function
that called TriggerNodeReport().

PR-URL: nodejs#26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@cjihrig
Copy link
Contributor Author

cjihrig commented Mar 4, 2019

@cjihrig cjihrig merged commit 31be552 into nodejs:master Mar 4, 2019
@cjihrig cjihrig deleted the report branch March 4, 2019 00:29
BridgeAR pushed a commit that referenced this pull request Mar 4, 2019
This commit uses the triggerReport() binding to handle
uncaught exceptions and removes the custom onUncaughtException
function.

PR-URL: #26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
BridgeAR pushed a commit that referenced this pull request Mar 4, 2019
PR-URL: #26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
BridgeAR pushed a commit that referenced this pull request Mar 4, 2019
This commit uses the triggerReport() binding to handle
signals and removes the custom onUserSignal() function.

PR-URL: #26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
BridgeAR pushed a commit that referenced this pull request Mar 4, 2019
PR-URL: #26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
BridgeAR pushed a commit that referenced this pull request Mar 4, 2019
trigger more accurately describes the use of the field.
Previously, location was just the name of the C++ function
that called TriggerNodeReport().

PR-URL: #26386
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@BridgeAR BridgeAR mentioned this pull request Mar 4, 2019
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. report Issues and PRs related to process.report.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants