diff options
| author | Bruno Larsen <blarsen@redhat.com> | 2022-05-13 13:23:57 -0300 |
|---|---|---|
| committer | Bruno Larsen <blarsen@redhat.com> | 2022-05-16 10:07:43 -0300 |
| commit | cdd4206647d0ef8d54d0fa66b3dfa57a4ec07db9 (patch) | |
| tree | be9e3ffcbe58cd24f751c1c828a91b8b79099784 /gdb/testsuite/gdb.cp/printmethod.exp | |
| parent | b7ff32f191ed7e708412e9faa31cf691f08ca695 (diff) | |
| download | gdb-cdd4206647d0ef8d54d0fa66b3dfa57a4ec07db9.zip gdb-cdd4206647d0ef8d54d0fa66b3dfa57a4ec07db9.tar.gz gdb-cdd4206647d0ef8d54d0fa66b3dfa57a4ec07db9.tar.bz2 | |
gdb/testsuite: fix "continue outside of loop" TCL errors
Many test cases had a few lines in the beginning that look like:
if { condition } {
continue
}
Where conditions varied, but were mostly in the form of ![runto_main] or
[skip_*_tests], making it quite clear that this code block was supposed
to finish the test if it entered the code block. This generates TCL
errors, as most of these tests are not inside loops. All cases on which
this was an obvious mistake are changed in this patch.
Diffstat (limited to 'gdb/testsuite/gdb.cp/printmethod.exp')
| -rw-r--r-- | gdb/testsuite/gdb.cp/printmethod.exp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.cp/printmethod.exp b/gdb/testsuite/gdb.cp/printmethod.exp index 70349d2..be597f5 100644 --- a/gdb/testsuite/gdb.cp/printmethod.exp +++ b/gdb/testsuite/gdb.cp/printmethod.exp @@ -19,7 +19,7 @@ # This file is part of the gdb testsuite -if { [skip_cplus_tests] } { continue } +if { [skip_cplus_tests] } { return } # # test running programs @@ -37,7 +37,7 @@ if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}]} { if ![runto_main] then { perror "couldn't run to breakpoint" - continue + return } # First, run to after we've constructed the object: |