Commit 75055de8 authored by Ian Lance Taylor's avatar Ian Lance Taylor

runtime: sleep a bit to let a bad signal be delivered

When we raise a signal that was delivered to C code, it's possible that
the kernel will not deliver it immediately. This is especially possible
on Darwin where we use send the signal to the entire process rather than
just the current thread. Sleep for a millisecond after sending the
signal to give it a chance to be delivered before we restore the Go
signal handler. In most real cases the program is going to crash at this
point, so sleeping is kind of irrelevant anyhow.

Fixes #14809.

Change-Id: Ib2c0d2c4e240977fb4535dc1dd2bdc50d430eb85
Reviewed-on: https://go-review.googlesource.com/33300
Run-TryBot: Ian Lance Taylor <iant@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: default avatarRuss Cox <rsc@golang.org>
parent e9ffda45
...@@ -354,6 +354,11 @@ func raisebadsignal(sig uint32, c *sigctxt) { ...@@ -354,6 +354,11 @@ func raisebadsignal(sig uint32, c *sigctxt) {
raise(sig) raise(sig)
// Give the signal a chance to be delivered.
// In almost all real cases the program is about to crash,
// so sleeping here is not a waste of time.
usleep(1000)
// If the signal didn't cause the program to exit, restore the // If the signal didn't cause the program to exit, restore the
// Go signal handler and carry on. // Go signal handler and carry on.
// //
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment