1 files changed, 56 insertions, 0 deletions
diff --git a/results/classifier/111/review/1771570 b/results/classifier/111/review/1771570
new file mode 100644
index 00000000..5b7a6ca4
--- /dev/null
+++ b/results/classifier/111/review/1771570
@@ -0,0 +1,56 @@
+other: 0.219
+semantic: 0.197
+files: 0.107
+device: 0.090
+performance: 0.062
+graphic: 0.062
+permissions: 0.044
+debug: 0.042
+boot: 0.035
+PID: 0.035
+network: 0.034
+socket: 0.034
+vnc: 0.025
+KVM: 0.014
+files: 0.212
+other: 0.156
+debug: 0.111
+PID: 0.077
+semantic: 0.074
+performance: 0.056
+KVM: 0.055
+network: 0.054
+device: 0.048
+permissions: 0.038
+socket: 0.036
+boot: 0.030
+vnc: 0.028
+graphic: 0.027
+
+qemu-aarch64 $program  > $file doesn't pipe output to file in 2.12.0
+
+Running qemu-aarch64 $program > $file doesn't pipe anything to $file. The file is created but empty.
+
+qemu-aarch64 --help > $file works, so piping output in my system seems to work.
+qemu-x86_64 $program > $file works, too.
+
+I'm running version 2.12.0 build from source with ./configure && make
+
+Output of uname -a:
+Linux zhostname>  4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
+
+Running "unbuffer qemu-aarch64 $program > $file" allows to pipe the output.
+
+Is it intentional that I need to disable buffering to allow piping to other processes? If yes, this issue can be closed.
+
+further reading about unbuffer: https://unix.stackexchange.com/questions/25372/turn-off-buffering-in-pipe#25378
+
+
+
+No, this should work on qemu-aarch64 the same way as for x86. I just tried redirection to a file with a sample program, and it worked fine for me. Can you provide a test case binary that fails like this, please?
+
+
+This issue is now marked as invalid, sorry for the trouble.
+
+qemu works just fine. The problem was with my linker configuration, it was using a different dynamic library for aarch64. Switching to a standard development stack solved my problem.
+