blob: 7ef01370332bf5b5e91ca6fd8410f445bbcae69c (
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 report is related to user-mode or system-mode in QEMU. Let me start by understanding the context.
The issue here is that when compiling a specific C++ program (nheko version 0.10.2-1) inside a chroot environment using qemu-aarch64-static, it results in a segmentation fault. The user provided strace output showing that cc1plus segfaults after some memory operations.
From the information given, it seems like QEMU is being used to run an x86_64 host compiling code for an aarch64 target within a chroot. The problem occurs when the C++ compiler's front-end (cc1plus) runs under QEMU's user-mode emulation.
In this scenario, QEMU is emulating the aarch64 CPU in user mode because it's executing the cc1plus binary which is for a different architecture. User-mode emulation typically deals with running individual processes and doesn't involve full OS virtualization or device emulation. The error happens during compilation, which is a userspace activity.
The strace output shows memory operations like brk and mmap, which are standard in process execution. The segfault occurs when accessing a certain address, suggesting an issue within the compiled code's execution under QEMU's user-mode environment.
Since there's no mention of device drivers, hardware emulation, or kernel-level issues, this seems isolated to how QEMU is handling the user-space binary execution. Therefore, it's likely a user-mode related bug.
</think>
user
|