summary refs log tree commit diff stats
path: root/results/classifier/118/none/1863445
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/none/1863445')
-rw-r--r--results/classifier/118/none/186344573
1 files changed, 73 insertions, 0 deletions
diff --git a/results/classifier/118/none/1863445 b/results/classifier/118/none/1863445
new file mode 100644
index 000000000..8fb302387
--- /dev/null
+++ b/results/classifier/118/none/1863445
@@ -0,0 +1,73 @@
+x86: 0.676
+TCG: 0.574
+debug: 0.540
+mistranslation: 0.473
+device: 0.454
+PID: 0.448
+socket: 0.412
+architecture: 0.385
+vnc: 0.378
+performance: 0.364
+VMM: 0.344
+hypervisor: 0.327
+ppc: 0.321
+kernel: 0.300
+user-level: 0.292
+arm: 0.292
+network: 0.288
+semantic: 0.272
+i386: 0.254
+virtual: 0.246
+register: 0.238
+risc-v: 0.219
+boot: 0.200
+assembly: 0.192
+permissions: 0.181
+files: 0.172
+peripherals: 0.134
+KVM: 0.133
+graphic: 0.110
+
+assertion failed at translate-all.c:2523 with version 3.1.1 
+
+I was trying to debug a userspace binary with radare2 and met the following assertion in qemu:
+
+```
+qemu-mipsel: /builddir/build/BUILD/qemu-3.1.1/accel/tcg/translate-all.c:2523: page_check_range: Assertion `start < ((target_ulong)1 << L1_MAP_ADDR_SPACE_BITS)' failed.
+qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x7fd1c11c5987
+```
+
+```
+# qemu-mipsel --version                                                                                   
+qemu-mipsel version 3.1.1 (qemu-3.1.1-2.fc30)
+Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
+```
+
+not much to add. seems like qemu is not properly checking for valid addresses
+
+
+
+in order to reproduce the bug:
+```
+qemu-mipsel -g 1234 ch67
+```
+
+and then juste launch (after installing r2):
+
+```
+r2 -a mips -b 32 -d gdb://127.0.0.1:1234
+```
+
+qemu will crash
+
+tested on fedora 30:
+```
+uname -a
+Linux bigfoot.home.ak42.io 5.4.18-100.fc30.x86_64 #1 SMP Fri Feb 7 14:37:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
+```
+
+Please try again with 4.2; there have been changes in this function.
+
+indeed, works fine with 4.2
+thanks
+