1 files changed, 79 insertions, 0 deletions
diff --git a/results/classifier/118/none/1738545 b/results/classifier/118/none/1738545
new file mode 100644
index 00000000..72234720
--- /dev/null
+++ b/results/classifier/118/none/1738545
@@ -0,0 +1,79 @@
+user-level: 0.736
+arm: 0.729
+semantic: 0.656
+architecture: 0.654
+graphic: 0.565
+debug: 0.548
+mistranslation: 0.475
+performance: 0.429
+files: 0.363
+x86: 0.314
+device: 0.311
+i386: 0.300
+PID: 0.280
+virtual: 0.272
+register: 0.265
+hypervisor: 0.264
+ppc: 0.262
+vnc: 0.261
+network: 0.235
+boot: 0.229
+kernel: 0.228
+risc-v: 0.222
+permissions: 0.204
+socket: 0.197
+TCG: 0.197
+VMM: 0.189
+assembly: 0.183
+peripherals: 0.154
+KVM: 0.136
+
+Go binaries panic with "mmap errno 9" on qemu-user
+
+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.
+
+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).
+
+
+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!
+
+I haven't tested sh4 specifically, but arm (subject of this bug report) definitely works, as does arm64.
+
+
+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.
+
+Could you file a separate bug for the sh4 case, then, please (with repro instructions)?
+
+
+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.
+