blob: 253597f1e2446e9751e23929414f6dbf3aac58c6 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to figure out whether this bug is related to user-mode or system-mode in QEMU. The user provided a Go program that panics with "mmap errno 9" when run under qemu-user. They mentioned it works on real hardware but not in the emulator.
First, let me understand what mmap does. Mmap is used for memory mapping files into memory, which is a common operation. Errno 9 corresponds to EADDRINUSE, but in this context, I think it's more about permissions or resource limits.
Since the issue occurs specifically when using gccgo-7 and running under qemu-user, it might be an emulation problem. QEMU has both user-mode (for cross-compiling) and system-mode (emulating a whole OS). Here, since they're compiling for armel and running on x86 via qemu-user, it's definitely user-mode.
The panic suggests that the mmap call is failing. Maybe there are resource limits or memory management issues in QEMU's user-mode emulator that aren't present when running natively. Real hardware works fine, so the problem isn't with Go or the program itself but how QEMU emulates the environment.
I don't see any mention of peripherals or higher-privilege operations; it's a basic mmap call failing. This points towards an issue in user-mode where certain system calls aren't handled correctly, leading to incorrect error returns.
</think>
user
|