blob: ae6bdfd3a5a692e7e2a77f45d53fdd4015efd8c1 (
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 QEMU bug is related to user-mode or system-mode. Let's see what the problem is.
The user reported that when they run a simple program using qemu-aarch64_be 9.1.0, it fails with an error message about gdb_find_static_feature() being unreachable. They provided the steps: compiling an empty.c file with specific flags and then running it with qemu.
Hmm, QEMU can run in two main modes: user-mode emulation and system-mode emulation. User-mode is for running individual programs without a full OS, while system-mode emulates a whole system including peripherals and devices.
In this case, the user is trying to run an executable directly with qemu-aarch64_be, which suggests they're using user-mode because it's just executing a binary without a full OS setup. The error occurs in gdbstub.c, which relates to debugging support. GDB stubs are used for debugging applications running under QEMU.
The error message mentions that the code shouldn't be reached, implying there's an issue with how features are being found in the debugger setup. Since this is about running a program and debugging it, it seems more like a user-mode issue rather than something related to system-wide emulation or hardware devices.
So, putting it all together, the problem is likely in user-mode because it's about executing a binary directly and interacting with the debugger in that context.
</think>
user
|