-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
src,lib: make ^C print a JS stack trace #29207
Conversation
Maybe we should only print a stack trace if stdin is a TTY (especially if it's meant to only happen when pressing ctrl-c)? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments but nice work!
503aca6
to
f175639
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
report:
is the subsystem for the node-report feature, i.e. node --experimental-report
… this touches a related topic, but I think it might be confusing to name it that way
Yes, this work doesn't touch |
@legendecas You can also use |
3797e8e
to
822e56a
Compare
124c8c3
to
b7ccab2
Compare
I think this PR is out of WIP, ready to be reviewed thoroughly :) |
@legendecas Looks like there are still issues with the postmortem tests… |
I'll try to fix it :P |
Concerns appear to have been addressed. Unresponsive to pings. Dismissing.
I will attempt to take a look but I am in transit today. If I don’t see it by mid Monday just go ahead. |
I don't have any substantive opinions for this. |
Since there are no objections anymore and multiple approves, I'd tag this as author-ready. |
If terminating the process with ctrl-c / SIGINT, prints a JS stacktrace leading up to the currently executing code. The feature would be enabled under option --trace-sigint. Conditions of no stacktrace on sigint: - has (an) active sigint listener(s); - main thread is idle (i.e. uv polling), a message instead of stacktrace would be printed.
Rebased to resolve conflicts. |
d5694b3
to
df403e3
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
If terminating the process with ctrl-c / SIGINT, prints a JS stacktrace leading up to the currently executing code. The feature would be enabled under option `--trace-sigint`. Conditions of no stacktrace on sigint: - has (an) active sigint listener(s); - main thread is idle (i.e. uv polling), a message instead of stacktrace would be printed. PR-URL: #29207 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Christopher Hiller <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Landed with 7b7e7bd 🎉 |
/cc @nodejs/tooling this landed 🎉 yay! we might want to talk about it in the next tooling WG meeting |
If terminating the process with ctrl-c / SIGINT, prints a JS stacktrace leading up to the currently executing code. The feature would be enabled under option `--trace-sigint`. Conditions of no stacktrace on sigint: - has (an) active sigint listener(s); - main thread is idle (i.e. uv polling), a message instead of stacktrace would be printed. PR-URL: #29207 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Christopher Hiller <[email protected]> Reviewed-By: Rich Trott <[email protected]>
If terminating the process with ctrl-c / SIGINT, prints a JS stacktrace leading up to the currently executing code. The feature would be enabled under option `--trace-sigint`. Conditions of no stacktrace on sigint: - has (an) active sigint listener(s); - main thread is idle (i.e. uv polling), a message instead of stacktrace would be printed. PR-URL: nodejs#29207 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Christopher Hiller <[email protected]> Reviewed-By: Rich Trott <[email protected]>
If terminating the process with ctrl-c / SIGINT, prints a JS stacktrace leading up to the currently executing code. The feature would be enabled under option `--trace-sigint`. Conditions of no stacktrace on sigint: - has (an) active sigint listener(s); - main thread is idle (i.e. uv polling), a message instead of stacktrace would be printed. PR-URL: #29207 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Christopher Hiller <[email protected]> Reviewed-By: Rich Trott <[email protected]>
If terminating the process with ctrl-c / SIGINT, prints a JS stack trace leading up to the currently executing code.
The feature would be enabled under option
--trace-sigint
.Conditions of no stacktrace on sigint:
Related: #24937
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes