blob: 2737c18121a564a996a38e5f6bd336e8f79fca84 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, let's try to figure out whether this bug is user-mode or system-mode related. The user reported that after upgrading QEMU from 2.10.1 to 2.11.1 on a Gentoo host, their uclibc-ng chroot environment started segfaulting when running Python and importing the portage module using qemu-arm in user mode.
They provided a backtrace showing where the segmentation fault occurs. The trace starts at `cpu_tb_exec` in `cpu-exec.c`, which is part of QEMU's TCG (Translation-Caching-Generator) acceleration. The error happens during code generation or execution within the emulator, not involving any hardware devices or system-level operations.
The user also mentioned that other chroots with glibc and musl don't have this issue, so it seems specific to uclibc-ng. They bisected QEMU and found a commit related to `MAX_RESERVED_VA` which they reverted to fix the problem. This suggests it's an issue within how QEMU handles memory or code generation for ARM in user mode.
Since the problem occurs when running user-space programs (like Python) inside the chroot using qemu-arm, and not when dealing with system-level operations like device emulation or higher privileges, this points towards a user-mode issue. The bug affects the execution of applications within the emulated environment without involving QEMU's system-mode features such as virtual devices or kernels.
Therefore, it's likely a user-mode related problem.
</think>
user
|