tree 70d6285fac6d5b7eb32b01fc294554819cb6c3af
parent d19e5493bd764e26a0662c06c858033a24eaa415
author Michael Anthony Knyszek <mknyszek@google.com> 1620144008 +0000
committer Michael Knyszek <mknyszek@google.com> 1620162976 +0000

runtime: abort when receiving a signal on a non-Go thread on Windows

Currently if a signal lands on a non-Go thread that's handled by the Go
handler, Go will emit a message. However, unlike everywhere else in the
runtime, Go will not abort the process after, and the signal handler
will try to continue executing.

This leads to cascading failures and possibly even memory corruption.

For #45638.

Change-Id: I546f4e82f339d555bed295528d819ac883b92bc6
Reviewed-on: https://go-review.googlesource.com/c/go/+/316809
Trust: Michael Knyszek <mknyszek@google.com>
Run-TryBot: Michael Knyszek <mknyszek@google.com>
Reviewed-by: Cherry Zhang <cherryyz@google.com>