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.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member
Could you file a separate bug for the sh4 case, then, please (with repro
instructions)?
--
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
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.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
I haven't tested sh4 specifically, but arm (subject of this bug report)
definitely works, as does arm64.
--
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
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!
--
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
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
