summary refs log tree commit diff stats
path: root/results/classifier/118/review/1761535
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/review/1761535')
-rw-r--r--results/classifier/118/review/1761535115
1 files changed, 115 insertions, 0 deletions
diff --git a/results/classifier/118/review/1761535 b/results/classifier/118/review/1761535
new file mode 100644
index 000000000..1089eb027
--- /dev/null
+++ b/results/classifier/118/review/1761535
@@ -0,0 +1,115 @@
+x86: 0.927
+debug: 0.893
+architecture: 0.890
+arm: 0.884
+device: 0.871
+peripherals: 0.856
+performance: 0.804
+ppc: 0.800
+files: 0.795
+risc-v: 0.776
+permissions: 0.763
+PID: 0.740
+socket: 0.739
+hypervisor: 0.734
+vnc: 0.727
+graphic: 0.694
+register: 0.678
+user-level: 0.653
+network: 0.636
+semantic: 0.630
+TCG: 0.619
+boot: 0.560
+kernel: 0.468
+mistranslation: 0.447
+VMM: 0.437
+KVM: 0.433
+i386: 0.411
+assembly: 0.389
+virtual: 0.384
+--------------------
+debug: 0.920
+arm: 0.801
+virtual: 0.578
+user-level: 0.544
+PID: 0.201
+hypervisor: 0.100
+files: 0.092
+TCG: 0.061
+performance: 0.046
+x86: 0.018
+register: 0.017
+socket: 0.009
+device: 0.009
+permissions: 0.008
+network: 0.008
+semantic: 0.007
+architecture: 0.007
+kernel: 0.005
+ppc: 0.004
+i386: 0.003
+boot: 0.003
+graphic: 0.002
+assembly: 0.002
+peripherals: 0.002
+vnc: 0.002
+VMM: 0.001
+risc-v: 0.001
+mistranslation: 0.000
+KVM: 0.000
+
+qemu-aarch64-static docker arm64v8/openjdk coredump
+
+I am using qemu-aarch64-static to run the arm64v8/openjdk official image on my x86 machine. Using QEMU master, I immediately hit a bug which hangs the container. With Ubuntu default version qemu-aarch64 version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.24) and qemu-aarch64 version 2.11.1 (v2.11.1-dirty) the hang does not take place.
+
+To reproduce (and get to the core dump):
+
+$ /tmp/tmptgyg3nvh/qemu-aarch64-static/qemu-aarch64-static -version
+qemu-aarch64 version 2.11.91 (v2.12.0-rc1-5-g47d3b60-dirty)
+Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
+
+$ docker run -it -v /tmp/tmptgyg3nvh/qemu-aarch64-static:/usr/bin/qemu-aarch64-static arm64v8/openjdk /bin/bash
+root@bf75cf45d311:/# javac
+Usage: javac <options> <source files>
+where possible options include:
+  -g                         Generate all debugging info
+<...snip...>
+  @<filename>                Read options and filenames from file
+
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+...TERMINAL HANGS...
+
+
+To get the core dump, In a separate terminal:
+
+# snapshot the file system of the hung image
+$ docker commit $(docker ps -aqf "name=latest_qemu") qemu_coredump
+
+# connect with known working qemu
+$ docker run -t -v /usr/bin/qemu-aarch64-static:/usr/bin/qemu-aarch64-static  -i qemu_coredump /bin/bash
+
+$$ ls -lat
+total 10608
+<snip>
+-rw-r--r--   1 root root 10792960 Mar 29 18:02 qemu_bash_20180329-180251_1.core
+drwxrwxrwt   5 root root     4096 Mar 29 18:02 tmp
+<snip>
+
+Could you provide a binary that we can use to reproduce, please? (preferably a setup that doesn't require me to figure out how to install and use docker...)
+
+
+I realized I had a javac lying around from last time somebody wanted me to debug a java problem, and I'm also seeing SEGVs with simpler programs like ls (!), so I'll have a look at those and hopefully that will be the same cause as what you're seeing.
+
+
+I think this should be fixed by https://patchwork.ozlabs.org/patch/896295/
+
+(incidentally the segfault is in the guest /bin/sh, not in javac or ls.)
+
+
+Now fixed in master, commit 7f0f4208b3a96, and will be in 2.12.0.
+
+
+Many thanks!
+
+I've just compiled master, and docker/aarch64/openjdk image now works as expected on my x86 machine.
+