Go binaries panic with "mmap errno 9" on qemu-user

[John Paul Adrian Glaubitz]

Go binaries panic with "mmap errno 9" on qemu-user.

root@nofan:/# cat hello.go
package main

import "fmt"

func main() {
    fmt.Println("hello world")
}
root@nofan:/# gccgo-7 hello.go -o hello
root@nofan:/# ./hello
mmap errno 9
fatal error: mmap

runtime stack:
mmap errno 9
fatal error: mmap
panic during panic

runtime stack:
mmap errno 9
fatal error: mmap
stack trace unavailable
root@nofan:/#

Tested with qemu from git master with Debian unstable for armel.

Same binaries work fine on real hardware.

[Peter Maydell (pmaydell)]

With current QEMU (and in particular with 4.1.0 rc3 or later with commit 5bfce0b74fbd5d5308 that fixes sigaltstack) go binaries work OK. I think we must have fixed this mmap issue at some point between when this bug was reported and now (or possibly the go runtime was made a bit more forgiving of QEMU's eccentricities).

[John Paul Adrian Glaubitz (glaubitz)]

Oh, that's interesting. I will verify this and if it indeed works, I will enable Go binaries for sh4 in Debian.

Thanks a lot for the update!

[Peter Maydell (pmaydell)]

I haven't tested sh4 specifically, but arm (subject of this bug report) definitely works, as does arm64.

[John Paul Adrian Glaubitz (glaubitz)]

I can confirm that the issue has been resolved on arm. Unfortunately, on sh4, the Go binaries are still crashing, albeit differently now. I verified that they work fine on real sh4 hardware.

[Peter Maydell (pmaydell)]

Could you file a separate bug for the sh4 case, then, please (with repro instructions)?

[Thomas Huth (th-huth)]

I'm marking this bug as "fix released" now since the Arm problem has been fixed. If there is something else to do for sh4, please open a new bug as suggested by Peter.