1 files changed, 53 insertions, 0 deletions
diff --git a/results/classifier/118/device/1738771 b/results/classifier/118/device/1738771
new file mode 100644
index 00000000..ac6eac25
--- /dev/null
+++ b/results/classifier/118/device/1738771
@@ -0,0 +1,53 @@
+device: 0.847
+x86: 0.828
+kernel: 0.747
+i386: 0.734
+files: 0.723
+architecture: 0.701
+user-level: 0.675
+performance: 0.646
+mistranslation: 0.640
+permissions: 0.616
+socket: 0.606
+semantic: 0.604
+graphic: 0.574
+network: 0.559
+register: 0.551
+PID: 0.514
+vnc: 0.495
+boot: 0.472
+ppc: 0.443
+risc-v: 0.425
+TCG: 0.362
+arm: 0.329
+peripherals: 0.319
+VMM: 0.318
+debug: 0.277
+virtual: 0.180
+KVM: 0.134
+hypervisor: 0.133
+assembly: 0.075
+
+qemu user does not provide AT_SECURE auxiliary vector entry
+
+When executing an android native binary using qemu in user mode, the program fail with the message
+
+FATAL: kernel did not supply AT_SECURE
+
+Android uses bionic libc.The linker requires that AT_SECURE is provided in the auxiliary vector, but qemu does not provide the entry.
+
+The issue can be reproduced using the commands:
+
+mkdir -p /tmp/android/system
+cd /tmp/android
+curl -O https://dl.google.com/android/repository/sys-img/google_apis/sysimg_x86-21_r15.zip
+unzip sysimg_x86-21_r15.zip
+mount -o loop x86/system.img system
+qemu-i386 -L /tmp/android/ system/bin/ls
+
+
+I've provided a patch (https://lists.gnu.org/archive/html/qemu-devel/2017-10/msg03667.html) to fix the issue, but it was not reviewed yet.
+
+A patch to add AT_SECURE went in and was released in QEMU 2.12.
+
+