diff options
author | Andrew Burgess <aburgess@redhat.com> | 2022-11-14 11:31:04 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2022-11-28 21:04:09 +0000 |
commit | 65a33d75c2667895f067cc5f9079215126cbb2eb (patch) | |
tree | fdd3f74defa60f3a0cb96123071d49990fd9cfe0 /gdb/testsuite/gdb.base/hbreak2.exp | |
parent | ed7fbdd033a272ff0d7d82c2153d7d0fade80d26 (diff) | |
download | binutils-gdb-65a33d75c2667895f067cc5f9079215126cbb2eb.tar.gz |
gdb/testsuite: remove use of then keyword from gdb.base/*.exp
The canonical form of 'if' in modern TCL is 'if {} {}'. But there's
still a bunch of places in the testsuite where we make use of the
'then' keyword, and sometimes these get copies into new tests, which
just spreads poor practice.
This commit removes all use of the 'then' keyword from the gdb.base/
test script directory.
There should be no changes in what is tested after this commit.
Diffstat (limited to 'gdb/testsuite/gdb.base/hbreak2.exp')
-rw-r--r-- | gdb/testsuite/gdb.base/hbreak2.exp | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gdb/testsuite/gdb.base/hbreak2.exp b/gdb/testsuite/gdb.base/hbreak2.exp index aecf613643d..a5e870a5708 100644 --- a/gdb/testsuite/gdb.base/hbreak2.exp +++ b/gdb/testsuite/gdb.base/hbreak2.exp @@ -25,7 +25,7 @@ if { [prepare_for_testing "failed to prepare" "hbreak2" {break.c break1.c} {debu set srcfile break.c set srcfile1 break1.c -if ![runto_main] then { +if {![runto_main]} { return } @@ -287,7 +287,7 @@ gdb_test "info break" \ #*********** -if ![runto_main] then { +if {![runto_main]} { return } @@ -315,7 +315,7 @@ gdb_test "hbreak" "Hardware assisted breakpoint \[0-9\]*.*" \ # Verify that a "silent" breakpoint can be set, and that GDB is indeed # "silent" about its triggering. # -if ![runto_main] then { +if {![runto_main]} { return } @@ -520,7 +520,7 @@ if { [prepare_for_testing "failed to prepare" "hbreak2o2" {break.c break1.c} {de return -1 } -if ![runto_main] then { +if {![runto_main]} { return } |