blob: 3f63f637978f47db8e8ca5852234481e9242030f (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I'm trying to figure out whether this bug in QEMU is related to user-mode or system-mode. Let's break it down.
The error message says "x86_64 linux-user: setup_rt_frame: not implemented". The term "linux-user" suggests that QEMU is running in user mode emulation, which means it's emulating a CPU for executing user-space applications without the full OS.
They're trying to run Parity (a blockchain client) under QEMU-x86_64 on an ARM machine. So the host is ARM, and they're using QEMU to emulate x86_64. The error occurs when running the binary directly with QEMU, which points towards user-mode since it's about executing a specific application.
The error mentions setup_rt_frame not being implemented. This likely relates to how signals or exceptions are handled in the emulation. Since it's during execution of an app, it's more about the CPU emulation rather than system-level components like devices or OS.
The crash is a segmentation fault (signal 11), which usually happens when accessing invalid memory addresses. In user-mode, QEMU emulates the CPU and handles instructions, so if setup_rt_frame isn't implemented, it might be missing some functionality needed for proper signal handling or context switching in user applications.
Considering that system-mode deals with higher-level stuff like devices and OS interactions, this seems more about running a specific binary and how the CPU handles it. So I think it's a user-mode issue.
</think>
user
|