-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Kill process by PID causing segfault in bash #1316
Comments
Can you try with the latest snapshot at https://wingit.blob.core.windows.net/files/index.html? |
Please also note that this is the correct invocation to kill MSYS2 programs, but for Win32 programs (such as |
Thank you. I'll try the snapshot in a minute. My script was using
|
Note that But I did not sit on my hands in the meantime, I investigated further and found out that the bug was introduced by some misguided "fix compiler warning" patch of mine. Will keep you posted. |
A crash when calling `kill <pid>` for a non-existing process [was fixed](git-for-windows/git#1316). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Turns out that these are actually not all that stupid (see git-for-windows/git#1316). We *have* to compile this code with -Wno-error=nonnull-compare. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Turns out that these comparisons are actually essential: otherwise e.g. `kill <pid>` will simply segfault if `<pid>` does not refer to an MSYS2 process (see git-for-windows/git#1316 for a real-world bug report). We *have* to compile this code with -Wno-error=nonnull-compare. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Setup
Details
Using Bash.
Process with specified PID should be killed, and Bash shouldn't segfault.
Bash segfaulted. Process with specified PID unaffected.
The text was updated successfully, but these errors were encountered: