diff options
Diffstat (limited to 'results/classifier/118/peripherals/1911')
| -rw-r--r-- | results/classifier/118/peripherals/1911 | 70 |
1 files changed, 70 insertions, 0 deletions
diff --git a/results/classifier/118/peripherals/1911 b/results/classifier/118/peripherals/1911 new file mode 100644 index 000000000..53655f2e2 --- /dev/null +++ b/results/classifier/118/peripherals/1911 @@ -0,0 +1,70 @@ +peripherals: 0.909 +mistranslation: 0.901 +hypervisor: 0.879 +graphic: 0.848 +TCG: 0.841 +KVM: 0.836 +semantic: 0.791 +vnc: 0.787 +user-level: 0.786 +debug: 0.779 +permissions: 0.769 +ppc: 0.763 +VMM: 0.750 +assembly: 0.743 +device: 0.723 +arm: 0.721 +x86: 0.695 +architecture: 0.690 +register: 0.687 +performance: 0.672 +boot: 0.629 +virtual: 0.604 +risc-v: 0.601 +PID: 0.597 +socket: 0.523 +network: 0.512 +i386: 0.397 +kernel: 0.390 +files: 0.373 + +abnormal segfaults inside qemu-system-riscv64 +Description of problem: +3 tests of Cockatrice segfaults in qemu-system-riscv64 emulator. This is similar to a regression of qemu-riscv64-static I reported: #1908. +But for qemu-system-riscv64, it doesn't looks like a recent regression because qemu 7.2.1 also fails. +Steps to reproduce: +To save the time on reproducing this bug, [I uploaded the zstd compressed qcow2 image to google drive](https://drive.google.com/file/d/1-2Wtmq4MlGvTLjmQ7P5vAvNlWg8--jjT/view?usp=sharing). It contains the whole environment, cockatrice source code and built tests. + +The password of the root user is `archriscv`. + +1. Setup Arch Linux riscv environment: https://github.com/CoelacanthusHex/archriscv-scriptlet https://github.com/felixonmars/archriscv-packages/wiki/Setup-Arch-Linux-RISC-V-using-qemu-system +2. Start it(with the commandline above, in the boot menu, choose `2: Linux linux (fallback initramfs)`) and building cockatrice with tests in it. +3. Run tests (/root/Cockatrice/build/tests/loading_from_clipboard/loading_from_clipboard_test, /root/Cockatrice/build/tests/carddatabase/filter_string_test, /root/Cockatrice/build/tests/carddatabase/carddatabase_test) +4. The tests segfault, which is unexpected. +Additional information: +The tests segfault at exactly the same instruction as in #1908: + +``` +┌──────────────────────────────────────────────────────────────────────────────┐ +│ > 0x7ffff2cba928 lhu a2,1248(a2) │ +│ 0x7ffff2cba92c and a0,a0,127 │ +│ 0x7ffff2cba930 sll a2,a2,0x7 │ +│ 0x7ffff2cba934 add a0,a0,a2 │ +│ 0x7ffff2cba938 lui t2,0xf8000 │ +│ 0x7ffff2cba93c lui a2,0xf5de2 │ +│ 0x7ffff2cba940 add a2,a2,-1824 │ +│ 0x7ffff2cba944 sll t2,t2,0x14 │ +│ 0x7ffff2cba948 xor a2,a2,t2 │ +│ 0x7ffff2cba94c sll t2,a0,0x1 │ +│ 0x7ffff2cba950 add a2,a2,t2 │ +│ 0x7ffff2cba954 lhu a2,0(a2) │ +│ 0x7ffff2cba958 sll a0,a2,0x3 │ +└──────────────────────────────────────────────────────────────────────────────┘ +multi-thre Thread 0x7ffff2cbe0 In: L?? PC: 0x7ffff2cba928 +(gdb) bt +#0 0x00007ffff2cba928 in () +``` + +It might suggest that 2d708164e0475064e0e2167bd73e8570e22df1e0 is not the true cause of #1908 and this bug shares the same underlying cause with #1908. + +Commit 2d708164e0475064e0e2167bd73e8570e22df1e0 LGTM, although it seems that it is copied from the loongarch one and the author forgot to update [the file header](https://gitlab.com/qemu-project/qemu/-/blob/2d708164e0475064e0e2167bd73e8570e22df1e0/linux-user/riscv/target_mman.h#L1-6). |