blob: c705f99f78e36ca6ff6de601f661e3ed65cc5e05 (
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 as either user-mode or system-mode related in QEMU. Let me start by understanding the problem.
The issue is that when using GDB to attach to a QEMU process (specifically qemu-x86_64) running in user mode, sending a Ctrl-C doesn't interrupt the emulation properly. The first Ctrl-C does nothing, and the second prompts whether to stop debugging.
I remember that in system-mode, QEMU emulates an entire system with its own kernel and devices, which involves higher privileges and more complex interactions. On the other hand, user-mode QEMU runs a single application without a full OS underneath.
In this case, the command used is `qemu-x86_64 -g 1234`, which suggests it's running in user mode because `-g` typically enables GDBstub for debugging an application. The binary being run is a static one that might pause or hang, but the issue is with how QEMU responds to interrupts from GDB.
Since this involves attaching via GDB and handling interrupt signals within the emulated application, it's likely related to user-mode emulation. System-mode would involve more about hardware devices or OS-level interactions, which isn't mentioned here.
</think>
The bug report pertains to user-mode emulation as it deals with GDB interaction and interrupt handling in a single-process environment without an underlying OS.
user
|