binutils-gdb/gdb/testsuite/gdb.mi/mi-until.exp
Bruno Larsen cdd4206647 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.
2022-05-16 10:07:43 -03:00

84 lines
2.6 KiB
Text

# Copyright 1999-2022 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# Test Machine interface (MI) operations
#
# Verify that, using the MI, we can run a simple program and perform
# exec-until.
#
# The goal is not to test gdb functionality, which is done by other
# tests, but to verify the correct output response to MI operations.
load_lib mi-support.exp
set MIFLAGS "-i=mi"
gdb_exit
if [mi_gdb_start] {
return
}
standard_testfile until.c
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
untested "failed to compile"
return -1
}
mi_delete_breakpoints
mi_gdb_reinitialize_dir $srcdir/$subdir
mi_gdb_reinitialize_dir $srcdir/$subdir
mi_gdb_load ${binfile}
proc test_running_to_foo {} {
set line [gdb_get_line_number "in-loop"]
mi_create_breakpoint $line \
"break-insert operation" \
-number 1 -func foo -file ".*until.c" -line $line
mi_run_cmd
mi_expect_stop "breakpoint-hit" "foo" "" ".*until.c" $line \
{ "" "disp=\"keep\"" } "run to main"
mi_gdb_test "100-break-delete 1" "100\\^done" "break-delete 1"
}
proc test_until {} {
setup_kfail gdb/2104 "*-*-*"
set line [gdb_get_line_number "after-loop"]
mi_execute_to "exec-until" "end-stepping-range" "foo" "" ".*until.c" $line "" \
"until after while loop"
set line [gdb_get_line_number "until-here"]
mi_execute_to "exec-until $line" "location-reached" "foo" "" ".*until.c" $line ""\
"until line number"
set line [gdb_get_line_number "until-there"]
mi_execute_to "exec-until until.c:$line" "location-reached" "foo" "" ".*until.c" $line ""\
"until line number:file"
# This is supposed to NOT stop at the return statement, but right
# after foo is over.
set line [gdb_get_line_number "at-return"]
mi_execute_to "exec-until until.c:$line" "location-reached" "main" ""\
".*until.c" "([expr $line-2]|[expr $line-1])" ""\
"until after current function"
}
test_running_to_foo
test_until
mi_gdb_exit
return 0