cmd/go: If strip the windows binary with binutils it won't run.

[jclab-joseph]

What version of Go are you using (go version)?

$ go version
go version go1.20.2 linux/amd64

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

go env Output

$ go env
GOARCH="amd64"
GOHOSTARCH="amd64"
GOOS="windows"
GOVERSION="go1.20.2"
GCCGO="gccgo"

What did you do?

See https://github.com/jclab-joseph/issue-go-windows-strip-not-working

The file built with the go build were stripped through binutils.
The stripped file runs on linux, but not on windows.
I'd like to keep the debug files separate to reduce the size.

What did you expect to see?

It should work on Windows PC.

What did you see instead?

[bcmills]

This doesn't seem like a cmd/go bug at all. If you're using binutils to modify a binary that runs, and it produces a binary that doesn't run, you should open an issue against binutils.

If you build a binary using the Go toolchain, and then you break that binary using a third-party tool, that's not the fault of the Go toolchain. 🙃

[jclab-joseph]

I don't think so... It always works fine except for go-lang.

Isn't go-lang producing non-generic binaries?