blob: f8a3f591a99acdf553af98a8b3cc7ceec0951ec7 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Alright, I need to classify this QEMU bug report as either user-mode or system-mode related. Let's start by understanding the issue.
The problem occurs when running binaries using `qemu-i386`, specifically those compiled for 32-bit x86 with TinyGo or Go. The symptoms include segmentation faults and internal errors in Go, like `mallocgc called without a P`. QEMU crashes, but only with the i386 target; x86_64 and arm work fine.
Looking at the backtraces, especially from older versions, it points to functions related to code translation and execution. For instance, `cpu_ldub_code` and `translator_loop` suggest issues in translating or executing user-space instructions. The error addresses (like 0x8000) indicate memory access problems within user-space.
Since the crash happens while running user binaries and not when handling system-level tasks like device emulation or OS booting, it's likely a user-mode issue. User-mode QEMU emulates the CPU and runs applications without full OS support, which aligns with the problem described here.
Therefore, this bug is related to user-mode operations in QEMU.
</think>
user
|