blob: d8e90a631a742192b20a520d0382cb4b9c54035d (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I need to classify this bug report about qemu-user emitting warnings that confuse userland applications into either a 'user-mode' or 'system-mode' issue. Let me think through this step by step.
First, the problem occurs when using qemu-sh4, which is part of the qemu-user package. This suggests it's related to user-mode emulation because qemu-user runs binaries for different architectures in a userspace environment without requiring full system virtualization.
The warnings from qemu-user are appearing on stdout or stderr, which are standard output streams used by userland applications. The configure script of OpenJDK-11 is getting confused by these messages, thinking they're part of its own output and causing errors. This directly affects the application's execution flow in user space.
If this were a system-mode issue, it would involve higher-level privileges or hardware emulation that impacts how the entire operating system runs. But here, the problem is within the application's interaction with qemu-user during its execution in user space.
Therefore, this bug report falls under 'user' because it relates to how userland applications interact with qemu in user mode without involving the full system virtualization aspects.
</think>
The issue involves qemu-user emitting warnings that interfere with userland applications, specifically affecting their operation during execution. This is a problem within the user-mode emulation environment.
user
|