blob: f0592593b21ef8d9fb1cb9a709013e4dcd988ef1 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Alright, I'm looking at this bug report involving QEMU. The user has provided a lot of information, including a coredump link. My task is to classify the bug as either 'user-mode' or 'system-mode'.
First, I'll go through the details given. The core dump shows that the process was running with various threads in different states. Some are in sigsuspend, syscall, __futex_abstimed_wait_cancelable64, and safe_syscall_base. These functions suggest it's dealing with system calls and thread synchronization.
Looking at the stack traces, most of them point to system-level functions rather than user applications. The fact that it's QEMU, which emulates hardware, indicates it might be interacting with device emulations or low-level system operations.
The presence of multiple threads and system call handling suggests this is more about how QEMU interacts with the underlying OS, possibly in a virtualized environment. This points towards system-mode issues since they often involve higher privileges and interactions with peripherals or devices.
I don't see any specific mentions of user-space applications failing; it's all related to internal QEMU processes and their interaction with the system. Therefore, this bug is likely system-mode related.
</think>
system
|