blob: 144375eb3ddbda0e3be9251182c7c93599581eb8 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to figure out whether this bug is related to user-mode or system-mode in QEMU. Let's see what the issue is about.
The problem occurs when running gcc-9 in an HPPA emulation using QEMU 5.0.0. The user provided a shell script and a preprocessed source file that cause gcc to crash with a segmentation fault. On real hardware, gcc works fine. They mentioned creating a hppa-user chroot environment with apt install.
So, the key points here are: it's about HPPA emulation (hppa-user), using user-mode QEMU because they're running a user space application (gcc) inside the chroot. The issue is that the compiler crashes in this environment but not on real hardware.
In QEMU, there are two main modes: user-mode and system-mode. User-mode emulates just the CPU and allows running user-space applications directly without a full OS boot. System-mode emulates the entire machine including peripherals, devices, and runs an OS.
Since the issue arises when compiling within a user chroot using hppa-user, it's likely related to how QEMU handles the HPPA instruction set in user-mode. The crash suggests there might be a bug in the CPU emulation specific to user applications.
Therefore, this bug is more about user-mode rather than system-mode because it's happening when running a user-space application without involving the full system-level emulations.
</think>
user
|