aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.fortran
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2023-01-18 12:09:05 +0000
committerAndrew Burgess <aburgess@redhat.com>2024-03-25 17:25:07 +0000
commit7879fba359f185d674d4e981af4f23a066bfe644 (patch)
tree0af3ef8dc583254d494f6c939ec400010eacb16b /gdb/testsuite/gdb.fortran
parentfe67b24240d7a679904c5bef3a7e911a09ea7739 (diff)
downloadbinutils-7879fba359f185d674d4e981af4f23a066bfe644.zip
binutils-7879fba359f185d674d4e981af4f23a066bfe644.tar.gz
binutils-7879fba359f185d674d4e981af4f23a066bfe644.tar.bz2
gdb: rename unwindonsignal to unwind-on-signal
We now have unwind-on-timeout and unwind-on-terminating-exception, and then the odd one out unwindonsignal. I'm not a great fan of these squashed together command names, so in this commit I propose renaming this to unwind-on-signal. Obviously I've added the hidden alias unwindonsignal so any existing GDB scripts will keep working. There's one test that I've extended to test the alias works, but in most of the other test scripts I've changed over to use the new name. The docs are updated to reference the new name. 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/testsuite/gdb.fortran')
-rw-r--r--gdb/testsuite/gdb.fortran/function-calls.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.fortran/function-calls.exp b/gdb/testsuite/gdb.fortran/function-calls.exp
index 3e698a5..e0b35d6 100644
--- a/gdb/testsuite/gdb.fortran/function-calls.exp
+++ b/gdb/testsuite/gdb.fortran/function-calls.exp
@@ -44,7 +44,7 @@ if {![runto [gdb_get_line_number "post_init"]]} {
}
# Use inspired by gdb.base/callfuncs.exp.
-gdb_test_no_output "set unwindonsignal on"
+gdb_test_no_output "set unwind-on-signal on"
# Baseline: function and subroutine call with no arguments.
gdb_test "p no_arg()" " = .TRUE."