summary refs log tree commit diff stats
path: root/results/classifier/108/other/1738771
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/108/other/1738771')
-rw-r--r--results/classifier/108/other/173877138
1 files changed, 38 insertions, 0 deletions
diff --git a/results/classifier/108/other/1738771 b/results/classifier/108/other/1738771
new file mode 100644
index 000000000..a43348dba
--- /dev/null
+++ b/results/classifier/108/other/1738771
@@ -0,0 +1,38 @@
+device: 0.847
+files: 0.723
+performance: 0.646
+permissions: 0.616
+socket: 0.606
+semantic: 0.604
+graphic: 0.574
+network: 0.559
+other: 0.554
+PID: 0.514
+vnc: 0.495
+boot: 0.472
+debug: 0.277
+KVM: 0.134
+
+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.
+
+