blob: c9974e6094b4997ff38db4a227d41710e4c0ad4a (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
<think>
Okay, so I'm trying to figure out whether this bug is related to user-mode or system-mode in QEMU. Let's start by understanding what the problem is.
The issue described involves a test program that segfaults when using QEMU 8.0.0 with coverage counters. The error happens during an instruction where it tries to store a value into a memory address, which seems valid because the previous check shows the address has some data (0x4fe9d0). However, after stepping through, it still causes a segfault.
Looking at the provided information:
1. **GDB Output**: The program is trying to increment a coverage counter using `str x8, [x9, #2512]`, where x8 is 1 and x9 points to an address in .bss section. The memory at that address exists but still causes a segfault.
2. **QEMU Versions**: Using QEMU 6.2.0 works without this particular issue, implying something changed between versions 6.2.0 and 8.0.0 that's causing the problem.
3. **Coverage Tools**: The test uses gcov with clang, which suggests it's about user-space code coverage rather than kernel or system-level stuff.
4. **Reproduction Steps**: It involves compiling a program statically with specific target flags for AArch64 and running it under QEMU. This points towards user-mode emulation since it's executing a regular application without OS involvement beyond the emulator.
5. **Bug Type**: Segfaults in user programs usually relate to how the CPU or memory is emulated in user mode, especially if it's about instruction execution or memory access.
Considering all this, the problem seems to be within how QEMU 8.0.0 handles certain instructions or memory accesses for user-space applications when coverage tools are involved. Since the crash happens while running a regular application without OS interaction beyond what's provided by the emulator, it's likely a user-mode issue.
So, classifying this as 'user' because it's about executing user-space code with specific compiler flags and coverage tools.
</think>
user
|