diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-16 16:59:00 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-16 16:59:33 +0000 |
| commit | 9aba81d8eb048db908c94a3c40c25a5fde0caee6 (patch) | |
| tree | b765e7fb5e9a3c2143c68b0414e0055adb70e785 /results/classifier/118/none/1812861 | |
| parent | b89a938452613061c0f1f23e710281cf5c83cb29 (diff) | |
| download | emulator-bug-study-9aba81d8eb048db908c94a3c40c25a5fde0caee6.tar.gz emulator-bug-study-9aba81d8eb048db908c94a3c40c25a5fde0caee6.zip | |
add 18th iteration of classifier
Diffstat (limited to 'results/classifier/118/none/1812861')
| -rw-r--r-- | results/classifier/118/none/1812861 | 58 |
1 files changed, 58 insertions, 0 deletions
diff --git a/results/classifier/118/none/1812861 b/results/classifier/118/none/1812861 new file mode 100644 index 00000000..c8bf2a69 --- /dev/null +++ b/results/classifier/118/none/1812861 @@ -0,0 +1,58 @@ +device: 0.769 +user-level: 0.720 +semantic: 0.692 +socket: 0.564 +arm: 0.549 +assembly: 0.548 +graphic: 0.532 +mistranslation: 0.528 +debug: 0.499 +ppc: 0.488 +vnc: 0.455 +boot: 0.450 +register: 0.426 +network: 0.424 +i386: 0.411 +PID: 0.399 +risc-v: 0.370 +kernel: 0.363 +architecture: 0.354 +x86: 0.315 +files: 0.304 +TCG: 0.302 +virtual: 0.293 +VMM: 0.220 +performance: 0.152 +KVM: 0.132 +permissions: 0.117 +peripherals: 0.095 +hypervisor: 0.092 + +QEMU in user-mode emulation mode crashes when the user program jumps to an invalid address + +Running this code: + +void (*func)() = 0x12345678; + +int main() +{ + func(); + return 0; +} + +Produces the following output: + +qemu-arm-static: /build/qemu-DqynNa/qemu-2.8+dfsg/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed. +qemu-arm-static: /build/qemu-DqynNa/qemu-2.8+dfsg/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed. +Segmentation fault + +The expected result is as follows: + +qemu: uncaught target signal 11 (Segmentation fault) - core dumped +Segmentation fault + + + +I'm not sure exactly when we fixed this (the fix is probably in the 4.1 release) but as of current head-of-git this correctly generates the SIGSEGV. + + |