diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2023-01-18 10:17:57 +0000 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2024-03-25 17:25:07 +0000 |
| commit | fe67b24240d7a679904c5bef3a7e911a09ea7739 (patch) | |
| tree | 7301f3990b22237c0e1672e714d4b3e4f037a241 /gdb/python/py-continueevent.c | |
| parent | 29f7ef927ad1ead740c7f4e3ae1375bff7e9a7e4 (diff) | |
| download | binutils-fe67b24240d7a679904c5bef3a7e911a09ea7739.zip binutils-fe67b24240d7a679904c5bef3a7e911a09ea7739.tar.gz binutils-fe67b24240d7a679904c5bef3a7e911a09ea7739.tar.bz2 | |
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 <eliz@gnu.org>
Tested-By: Luis Machado <luis.machado@arm.com>
Tested-By: Keith Seitz <keiths@redhat.com>
Diffstat (limited to 'gdb/python/py-continueevent.c')
0 files changed, 0 insertions, 0 deletions