summary refs log tree commit diff stats
path: root/results/classifier/118/device/1072
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/device/1072')
-rw-r--r--results/classifier/118/device/107254
1 files changed, 54 insertions, 0 deletions
diff --git a/results/classifier/118/device/1072 b/results/classifier/118/device/1072
new file mode 100644
index 000000000..5e99353ce
--- /dev/null
+++ b/results/classifier/118/device/1072
@@ -0,0 +1,54 @@
+device: 0.903
+graphic: 0.836
+performance: 0.834
+architecture: 0.826
+debug: 0.813
+files: 0.775
+PID: 0.659
+kernel: 0.655
+network: 0.650
+socket: 0.634
+semantic: 0.634
+arm: 0.630
+register: 0.625
+x86: 0.595
+peripherals: 0.589
+permissions: 0.575
+vnc: 0.572
+hypervisor: 0.559
+ppc: 0.553
+i386: 0.489
+TCG: 0.479
+risc-v: 0.471
+user-level: 0.449
+VMM: 0.419
+virtual: 0.339
+boot: 0.328
+KVM: 0.313
+mistranslation: 0.301
+assembly: 0.207
+
+different behavior when remote debugger is used
+Description of problem:
+I found Qemu shows different behavior when I run Qemu with hello-world (statically linked binary enclosed) directly or run it through remote debugger. I need help to understand the following: 
+
+1. Is this intended behavior?
+1. Any way to make the two approaches have consistent behavior (I prefer the behavior shown in the 2nd approach described below)
+1. If it is intended behavior, any explanation why or suggestions how to dig further to root cause the difference.
+
+The corresponding source code is the line 86 in [filedoalloc.c](https://code.woboq.org/userspace/glibc/libio/filedoalloc.c.html#86). It tests if the file (stdout) is char special device (S_ISCHR)
+The preprocessed code is as follows:
+   if (((((st.st_mode)) & 0170000) == (0020000))) 
+
+I then compared two different approaches to run Qemu:
+
+1. I used the following command line to collect the trace:  qemu_aarch64 -strace  -plugin $QEMU_ROOT/build/contrib/plugins/libexeclog.so -d plugin hello.a64. This one tests False for S_ISCHR
+1. when I used gdb to connect to Qemu and single-step the instructions, S_ISCHR tests True, which is different from running qemu directly (approach 1). 
+
+Thanks!
+Steps to reproduce:
+1.[hello.a64](/uploads/4b4ccae8c1e4b045c39ceae6a094d55a/hello.a64)
+2.
+3.
+Additional information:
+