1 files changed, 0 insertions, 29 deletions

diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1725.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1725.toml
deleted file mode 100644
index fa432cf4..00000000
--- a/gitlab/issues/target_missing/host_missing/accel_missing/1725.toml
+++ /dev/null
@@ -1,29 +0,0 @@
-id = 1725
-title = "qemu-system-x86_64 reports wrong thread to GDB on SIGINT"
-state = "closed"
-created_at = "2023-06-23T17:34:54.954Z"
-closed_at = "2023-08-31T16:14:26.071Z"
-labels = ["GDB", "workflow::Patch available"]
-url = "https://gitlab.com/qemu-project/qemu/-/issues/1725"
-host-os = "Arch Linux"
-host-arch = "x86_64"
-qemu-version = "8.0.2 (v8.0.2)"
-guest-os = "Linux (Also happens in SeaBIOS)"
-guest-arch = "x86_64"
-description = """Upon interruption of a thread by GDB, QEMU in some circumstances will send a stop reply with the ID of a thread that had not been resumed.
-
-This happens for the following reasons:
-1. GDB uses `vCont` exclusively to resume and step through threads.
-2. When a thread is interrupted by GDB, QEMU runs `vm_stop(RUN_STATE_PAUSED)`, which triggers `gdb_vm_state_change`, which, in turn, uses whatever CPU is pointed to by `gdbserver_state.c_cpu` at that time to construct the stop reply.
-3. The `vCont` handler in QEMU doesn't set `gdbserver_state.c_cpu` before resuming any CPUs.
-
-Important to note is that stepping is not affected by this issue because the `EXCP_DEBUG` handler sets `gdbserver_state.c_cpu` to the CPU the exception happened in before `gdb_vm_state_change` runs. Which also means single stepping before continuing is an effective way to work around this bug."""
-reproduce = """1. Run QEMU with at least two threads and the GDB stub enabled.
-2. Run `gdb --nx --ex 'target remote :1234' --ex 'set scheduler-locking on'`
-3. Switch to Thread 1.2 in GDB with `thr 2`
-4. Resume Thread 1.2 in GDB with `c`
-5. Press Ctrl+C to interrupt the VM
-6. Notice that the event is reported as having happened in Thread 1.1, which has not been resumed."""
-additional = """Note that, while this bug happens no matter the state of `scheduler-locking`, it only becomes a problem when it is enabled. This is because, when it is disabled, GDB will always resume all threads on `continue`, so it doesn't matter what thread ID QEMU says the interrupt happened in, as it is guaranteed to have been resumed anyway. That, however, is not the case when `scheduler-locking` is enabled.
-
-Regardless, I don't think it makes sense for QEMU to be reporting events happening in threads that weren't resumed through either `s/S/c/C` or `vCont`, which is what it's doing here."""