summary refs log tree commit diff stats
path: root/gitlab/issues_text/target_missing/host_missing/accel_missing/2924
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/2924')
-rw-r--r--gitlab/issues_text/target_missing/host_missing/accel_missing/292415
1 files changed, 15 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2924 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2924
new file mode 100644
index 000000000..75328c2b2
--- /dev/null
+++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2924
@@ -0,0 +1,15 @@
+qemu-user not responding to Ctrl-C from gdb
+Description of problem:
+When attached to qemu-x84_64's gdbserver via gdb, it is not possible to interrupt the binary being emulated. Usually, Ctrl-C will interrupt a running binary from gdb and I believe (though have not tested) it works in qemu-system.
+
+First Ctrl-C will do nothing and second will prompt to stop debugging.
+```
+(gdb) c
+Continuing.
+^C^CThe target is not responding to interrupt requests.
+Stop debugging it? (y or n)
+```
+Steps to reproduce:
+1. Run `./qemu-x86_64 -g 1234 ~/Downloads/base64-x64_64-static` or any static binary that will pause/hang
+2. Connect from gdb `(gdb) target remote :1234`
+3. Ctrl-C in gdb