/ go Public
runtime: badsignal2 crash on windows/arm64 #56080
Issues related to the Go compiler and/or runtime.
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
Does this issue reproduce with the latest release?
Yes, with the latest major version (1.19).
What operating system and processor architecture are you using (
What did you do?
I ran a Golang program that uses a DLL that raises a Windows exception in a non-Golang thread. This results in a call to
What did you expect to see?
I expected to see the message
runtime: signal received on thread not created by Go.
What did you see instead?
An Access Violation in
Problem and solution
The problem is that
WriteFileexpects a valid pointer for the
badsignal2seems to initialize the
x3register (which contains the
lpNumberOfBytesWrittenargument) to a bogus value.
The solution is to properly initialize
x3prior to calling
The text was updated successfully, but these errors were encountered: