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).
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1738545
Title:
Go binaries panic with "mmap errno 9" on qemu-user
Status in QEMU:
Fix Committed
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1738545/+subscriptions
