From fe67b24240d7a679904c5bef3a7e911a09ea7739 Mon Sep 17 00:00:00 2001 From: Andrew Burgess Date: Wed, 18 Jan 2023 10:17:57 +0000 Subject: gdb: introduce unwind-on-timeout setting Now that inferior function calls can timeout (see the recent introduction of direct-call-timeout and indirect-call-timeout), this commit adds a new setting unwind-on-timeout. This new setting is just like the existing unwindonsignal and unwind-on-terminating-exception, but the new setting will cause GDB to unwind the stack if an inferior function call times out. The existing inferior function call timeout tests have been updated to cover the new setting. Reviewed-By: Eli Zaretskii Tested-By: Luis Machado Tested-By: Keith Seitz --- gdb/NEWS | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'gdb/NEWS') diff --git a/gdb/NEWS b/gdb/NEWS index a41a72b..72ec979 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -72,6 +72,15 @@ show indirect-call-timeout ignored, GDB will wait indefinitely for an inferior function to complete, unless interrupted by the user using Ctrl-C. +set unwind-on-timeout on|off +show unwind-on-timeout + These commands control whether GDB should unwind the stack when a + timeout occurs during an inferior function call. The default is + off, in which case the inferior will remain in the frame where the + timeout occurred. When on, GDB will unwind the stack removing the + dummy frame that was added for the inferior call, and restoring the + inferior state to how it was before the inferior call started. + * New features in the GDB remote stub, GDBserver ** The --remote-debug and --event-loop-debug command line options -- cgit v1.1