aboutsummaryrefslogtreecommitdiff
path: root/gdbstub/system.c
diff options
context:
space:
mode:
authorAlex Bennée <alex.bennee@linaro.org>2023-12-01 09:36:27 +0000
committerAlex Bennée <alex.bennee@linaro.org>2023-12-01 14:00:52 +0000
commit5dcf6334ae1af158ec149794c3f35e459b98df5e (patch)
tree58d457341d13e2102edc1ee9174ef3ba83bada31 /gdbstub/system.c
parentabf635ddfe3242df907f58967f3c1e6763bbca2d (diff)
gdbstub: use a better signal when we halt for IO reasons
The gdb description GDB_SIGNAL_IO is "I/O possible" and by default gdb will try and restart the guest, getting us nowhere. Report GDB_SIGNAL_STOP instead which should at least halt the session at the failure point. Reviewed-by: Luis Machado <luis.machado@arm.com> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Acked-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20231201093633.2551497-2-alex.bennee@linaro.org>
Diffstat (limited to 'gdbstub/system.c')
-rw-r--r--gdbstub/system.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdbstub/system.c b/gdbstub/system.c
index 783ac140b9..83fd452800 100644
--- a/gdbstub/system.c
+++ b/gdbstub/system.c
@@ -183,7 +183,7 @@ static void gdb_vm_state_change(void *opaque, bool running, RunState state)
break;
case RUN_STATE_IO_ERROR:
trace_gdbstub_hit_io_error();
- ret = GDB_SIGNAL_IO;
+ ret = GDB_SIGNAL_STOP;
break;
case RUN_STATE_WATCHDOG:
trace_gdbstub_hit_watchdog();