blob: 9b764743a64a8248a2bbe0a6b2170ac7be24eaff (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, so I'm trying to figure out whether this qemu-mips64 Segmentation fault is a user-mode or system-mode issue. Let me start by understanding the problem.
The user ran `./qemu-mips64 ../lang` and got a segmentation fault. The error message says "uncaught target signal 11 (Segmentation fault) - core dumped." So, it seems like QEMU is crashing when trying to run their MIPS64 executable.
I know that QEMU can run in two modes: user-mode and system-mode. User-mode emulation allows running individual programs without a full OS, while system-mode emulates the entire system, including hardware devices and peripherals.
In this case, the command used was `qemu-mips64`, which is typically for user-mode since it's meant to run binaries directly. The error occurs when trying to execute a MIPS64 executable, suggesting that there might be an issue with how QEMU handles the binary in user-mode.
I should check if others have encountered similar issues. Maybe it's a known bug. I'll look up "qemu-mips64 segmentation fault" and see what comes up. It appears there are reports of segfaults when running certain binaries, especially older or specific ones that might not be fully supported in user-mode.
Since the error is about signal 11, which is a segmentation fault, it's likely related to how QEMU translates or executes the MIPS64 instructions. User-mode doesn't require full system emulation, so issues here would fall under user-mode bugs.
Therefore, this bug report should be classified as 'user' mode.
</think>
user
|