-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
os/signal: deadlock combining signal handling with syscall.AllThreadsSyscall #43149
Labels
Milestone
Comments
Please assign this bug to me. I have a fix. |
Change https://golang.org/cl/277434 mentions this issue: |
ianlancetaylor
added
the
NeedsFix
The path to resolution is known, but the work has not been done.
label
Dec 12, 2020
hecg119
pushed a commit
to hecg119/libcap
that referenced
this issue
Mar 17, 2021
Avoid building any of the GO stuff: make GOLANG=no ... Build with a specific build of GO: make GO=~/sdk/go1.16rc1/bin/go ... Also, now golang/go#43149 is resolved in the go1.16rc1 build (it does not work in the go1.16beta1 but we don't support that one any more), remove the forced CGO use for the go/psx-signals build. Signed-off-by: Andrew G. Morgan <morgan@kernel.org>
For the record, #44193 does represent remaining issues with this support in 1.16. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
No. It is a failure introduced with the new syscall.AllThreadsSyscall*() functions.
What operating system and processor architecture are you using (
go env
)?What did you do?
Following this bug: https://bugzilla.kernel.org/show_bug.cgi?id=210533 (which did not relate to the golang sources) I tried to test signal handling with the new (post 1.15)
syscall.AllThreadsSyscall*()
by adding the following test to the golang tree:Then in a build tree with this added test case I built and ran it as follows:
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: