src: fix syntax error not showing in stderr with node --inspect-brk #42486
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed #41792
When an uncaught exception occurs with inspector enabled,
node::errors::TriggerUncaughtException
will let an inspector agent send the error report.node/src/node_errors.cc
Line 336 in 6e54851
After reporting errors, the inspector agent waits for the client to disconnect. But this means the agent stops the following process and shows nothing in stderr.
Ideally,
AtExit
hook should be responsible for disconnection of inspector and the error reporters should send error information only. An inspector agent has no reason to wait for disconnection since the disconnection process is already registered toAtExit
hook.node/src/inspector_agent.cc
Lines 711 to 716 in 6e54851