1 files changed, 42 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1746943 b/results/classifier/zero-shot/108/other/1746943
new file mode 100644
index 000000000..a37f6191c
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1746943
@@ -0,0 +1,42 @@
+graphic: 0.853
+device: 0.843
+performance: 0.839
+semantic: 0.729
+other: 0.725
+network: 0.582
+permissions: 0.558
+socket: 0.547
+vnc: 0.384
+debug: 0.354
+files: 0.295
+PID: 0.247
+boot: 0.206
+KVM: 0.015
+
+qemu-aarch64-static: qemu: uncaught target signal 11 for ps/top cmd
+
+In a docker container created from an aarch64 image, injects qemu-aarch64-static (in /usr/bin)
+  run ps/top cmd  inside this container
+
+  reports "qemu: uncaught target signal 11 (Segmentation fault)"
+
+Tried qemu-aarch64-static from fedora 27 / ubuntu artful / debian unstable (i.e. qemu version 2.10 - 2.11)
+
+The aarch64 dock image is fedora 27(and with qemu-aarch64-static Fedora 27), hence I opened a related bug here https://bugzilla.redhat.com/show_bug.cgi?id=1541252
+
+I tried psproc-ng from https://launchpad.net/ubuntu/+source/procps/2:3.3.12-1ubuntu2/+build/10452812
+
+No SEGV, I guess it may be a CRASH-PATH which is triggered in this specific scenario
+
+I've did update in redhat bugzilla #1541252, and wait for confirming above.
+
+BTW, "uncaught target signal 11" makes it hard to figure out "how this SEGV happened"
+
+Could you provide instructions to reproduce that don't require Fedora or docker, please?
+
+
+Still waiting for repro instructions (eg attaching a binary that doesn't run under QEMU).
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+