-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
child_process.spawnSync returns status=0 when signal=SIGKILL #11284
Labels
child_process
Issues and PRs related to the child_process subsystem.
Comments
mscdex
added
the
child_process
Issues and PRs related to the child_process subsystem.
label
Feb 10, 2017
3 tasks
Proposed fix in #11288. |
cjihrig
added a commit
to cjihrig/node
that referenced
this issue
Feb 14, 2017
This commit sets the spawnSync() exit code to null when the child is killed via signal. This brings the behavior more in sync with spawn(). Fixes: nodejs#11284 PR-URL: nodejs#11288 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Evan Lucas <[email protected]>
italoacasas
pushed a commit
to italoacasas/node
that referenced
this issue
Feb 16, 2017
This commit sets the spawnSync() exit code to null when the child is killed via signal. This brings the behavior more in sync with spawn(). Fixes: nodejs#11284 PR-URL: nodejs#11288 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Evan Lucas <[email protected]>
italoacasas
pushed a commit
that referenced
this issue
Feb 22, 2017
This commit sets the spawnSync() exit code to null when the child is killed via signal. This brings the behavior more in sync with spawn(). Fixes: #11284 PR-URL: #11288 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Evan Lucas <[email protected]>
jasnell
pushed a commit
that referenced
this issue
Mar 7, 2017
This commit sets the spawnSync() exit code to null when the child is killed via signal. This brings the behavior more in sync with spawn(). Fixes: #11284 PR-URL: #11288 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Evan Lucas <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Mar 9, 2017
This commit sets the spawnSync() exit code to null when the child is killed via signal. This brings the behavior more in sync with spawn(). Fixes: #11284 PR-URL: #11288 Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Evan Lucas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the process forked by
child_process.spawnSync
is send SIGKILL, the returned object hasstatus == 0
whilesignal == SIGKILL
. This differs from the behavior ofchild_process.spawn
, for which the Exit event handler is called withstatus == null
andsignal == SIGKILL
, per the documentation.Reproduction at https://github.com/brandones/nodejs-child-process-bug-repro
The text was updated successfully, but these errors were encountered: