We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From waitpid(2):
WEXITSTATUS(status) returns the exit status of the child. [...] This macro should only be employed if WIFEXITED returned true.
dumb-init does not check WIFEXITED before calling WEXITSTATUS, which could lead to funny behaviour when the child process is terminated by a signal.
The text was updated successfully, but these errors were encountered:
@msavage20 thanks for the report!
here's the non-dumb-init behavior:
ckuehl@dev18-devc:~$ python -c 'while True: pass' [in another terminal, send SIGTERM to python] ckuehl@dev18-devc:~$ echo $? 143
and the dumb-init behavior:
ckuehl@dev18-devc:~$ dumb-init python -c 'while True: pass' [in another terminal, send SIGTERM to python] ckuehl@dev18-devc:~$ echo $? 0
I'll start preparing a patch.
Sorry, something went wrong.
I don't know much about this corner of posix/C, but the logic looks good.
d626878
fix released in v1.0.1, thanks again for the report!
No branches or pull requests
From waitpid(2):
dumb-init does not check WIFEXITED before calling WEXITSTATUS, which could lead to funny behaviour when the child process is terminated by a signal.
The text was updated successfully, but these errors were encountered: