blob: 6918edd885313056ceaeec249fa54929e014e439 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Alright, let's try to figure out whether this bug is user-mode or system-mode related. The report mentions a segfault when running a cross-compiled binary using qemu-riscv64. It includes information about the coredump and a reproducer with testb3 and sysroot.
Looking at the backtrace provided, it shows functions like cpu_loop, clone_func, and various gdbstub functions. These are typically part of the user-mode emulation because they deal with CPU loops and debugging stubs for userspace programs. The issue seems to occur within the context of running a specific application (testb3) which is likely a userspace program.
The coredump and binary provided are for qemu-riscv64, which suggests it's related to how qemu handles user-mode execution for RISC-V binaries. There's no mention of hardware emulation, devices, or OS-level issues, which would be more indicative of system-mode problems.
Given all this, the bug is likely within the user-mode emulation part of QEMU.
</think>
user
|