aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base/ena-dis-br.exp
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-11-14 11:31:04 +0000
committerAndrew Burgess <aburgess@redhat.com>2022-11-28 21:04:09 +0000
commit65a33d75c2667895f067cc5f9079215126cbb2eb (patch)
treefdd3f74defa60f3a0cb96123071d49990fd9cfe0 /gdb/testsuite/gdb.base/ena-dis-br.exp
parented7fbdd033a272ff0d7d82c2153d7d0fade80d26 (diff)
downloadgdb-65a33d75c2667895f067cc5f9079215126cbb2eb.zip
gdb-65a33d75c2667895f067cc5f9079215126cbb2eb.tar.gz
gdb-65a33d75c2667895f067cc5f9079215126cbb2eb.tar.bz2
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/ena-dis-br.exp')
-rw-r--r--gdb/testsuite/gdb.base/ena-dis-br.exp16
1 files changed, 8 insertions, 8 deletions
diff --git a/gdb/testsuite/gdb.base/ena-dis-br.exp b/gdb/testsuite/gdb.base/ena-dis-br.exp
index 93ac124..8900f53 100644
--- a/gdb/testsuite/gdb.base/ena-dis-br.exp
+++ b/gdb/testsuite/gdb.base/ena-dis-br.exp
@@ -34,7 +34,7 @@ set bp_location14 [gdb_get_line_number "set breakpoint 14 here" $srcfile2]
set bp_location15 [gdb_get_line_number "set breakpoint 15 here" $srcfile2]
set bp_location17 [gdb_get_line_number "set breakpoint 17 here" $srcfile2]
-if ![runto_main] then {
+if {![runto_main]} {
return
}
@@ -123,7 +123,7 @@ gdb_continue_to_end "no stop at auto-disabled break marker2"
# Verify that we can set a breakpoint to be self-deleting after the
# first time it triggers.
-if ![runto_main] then {
+if {![runto_main]} {
return
}
@@ -154,7 +154,7 @@ gdb_test "info break $bp" \
"\[0-9\]*\[ \t\]+breakpoint\[ \t\]+keep\[ \t\]+n.*" \
"info break marker4"
-if ![runto_main] then {
+if {![runto_main]} {
return
}
@@ -193,7 +193,7 @@ gdb_test "continue" \
# should cause the next N triggers of the bp to be ignored. (This is
# a flavor of enablement/disablement, after all.)
-if ![runto_main] then {
+if {![runto_main]} {
return
}
@@ -254,7 +254,7 @@ gdb_test_multiple "continue" "$test" {
# Verify that we can specify both an ignore count and an auto-delete.
-if ![runto_main] then {
+if {![runto_main]} {
return
}
@@ -286,7 +286,7 @@ gdb_test "continue" \
# Verify that a disabled breakpoint's ignore count isn't updated when
# the bp is encountered.
-if ![runto_main] then {
+if {![runto_main]} {
return
}
@@ -315,7 +315,7 @@ gdb_test "info break $bp" \
# (Also verify that GDB gracefully handles the case where the inferior
# isn't stopped at a breakpoint.)
#
-if ![runto_main] then {
+if {![runto_main]} {
return
}
@@ -343,7 +343,7 @@ gdb_test_multiple "continue 2" "$test" {
# Verify that GDB correctly handles the "enable/disable" command
# with arguments, that include multiple locations.
#
-if ![runto_main] then {
+if {![runto_main]} {
return
}