1 files changed, 53 insertions, 0 deletions
diff --git a/results/classifier/108/other/1318281 b/results/classifier/108/other/1318281
new file mode 100644
index 00000000..45637fff
--- /dev/null
+++ b/results/classifier/108/other/1318281
@@ -0,0 +1,53 @@
+graphic: 0.798
+performance: 0.779
+device: 0.693
+semantic: 0.676
+other: 0.626
+files: 0.466
+permissions: 0.362
+debug: 0.351
+PID: 0.321
+network: 0.316
+vnc: 0.315
+boot: 0.285
+socket: 0.252
+KVM: 0.077
+
+linux-user: x86_64 target fails to call sys_futex()
+
+I'm building the latest QEMU (06b4f00d53637f2c16a62c2cbaa30bffb045cf88) on ARM to run some x86_64 executables in user mode. This is my configuration:
+
+./configure \
+  --prefix=/root/qemu-x86_64 \
+  --target-list=x86_64-linux-user \
+  --disable-system \
+  --disable-tools
+
+The following program is used for testing:
+
+https://gist.github.com/hujiajie/e8cff43b574b399c8f59#file-test-c
+
+I compile the test program in Debian-7.5-amd64 like this:
+
+gcc -o test `pkg-config --cflags glib-2.0` test.c `pkg-config --static --libs glib-2.0` -static
+
+and launch the program on ARM with
+
+qemu-x86_64 test
+
+The test crashes with the following message:
+
+qemu: uncaught target signal 11 (Segmentation fault) - core dumped
+Segmentation fault
+
+The output of `strace qemu-x86_64 test` is here:
+
+https://gist.github.com/hujiajie/88d1d5e580d432d11b2d#file-test-strace-log
+
+It seems that the error is caused by the failure of the futex syscall.
+
+qemu-i386 could launch the 32-bit test perfectly, the problem only happens on a x86_64 target.
+
+The test program works fine with current git master, so I think we have fixed this bug at some point in the last two years.
+
+