diff options
Diffstat (limited to 'gdb/testsuite/gdb.base/structs.exp')
| -rw-r--r-- | gdb/testsuite/gdb.base/structs.exp | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/gdb/testsuite/gdb.base/structs.exp b/gdb/testsuite/gdb.base/structs.exp index 31a45b5..4850a59 100644 --- a/gdb/testsuite/gdb.base/structs.exp +++ b/gdb/testsuite/gdb.base/structs.exp @@ -56,7 +56,7 @@ proc start_structs_test { types } { } set binfile [standard_output_file ${testfile}] - if { [prepare_for_testing "failed to prepare" $binfile $srcfile $flags] } { + if { [prepare_for_testing "failed to prepare" $testfile $srcfile $flags] } { return -1 } @@ -75,7 +75,7 @@ proc start_structs_test { types } { get_debug_format # Limit the slow $anychar_re{256} matching for better performance. - if $first { + if {$first} { set first 0 # Verify $anychar_re can match all the values of `char' type. @@ -215,7 +215,7 @@ proc test_struct_calls { n } { # Check that GDB can always extract a struct-return value from an # inferior function call. Since GDB always knows the location of an # inferior function call's return value these should never fail - + # Implemented by calling the parameterless function "fun$N" and then # examining the return value printed by GDB. @@ -364,7 +364,7 @@ proc test_struct_returns { n } { pass "${test}" } -re " = [any $n].*${gdb_prompt} $" { - if $return_value_known { + if {$return_value_known} { # This contradicts the above claim that GDB knew # the location of the return value. fail "${test}" @@ -375,7 +375,7 @@ proc test_struct_returns { n } { } } -re ".*${gdb_prompt} $" { - if $return_value_unimplemented { + if {$return_value_unimplemented} { # What a surprise. The architecture hasn't implemented # return_value, and hence has to fail. kfail "$test" gdb/1444 @@ -383,8 +383,8 @@ proc test_struct_returns { n } { fail "$test" } } - } - + } + # Check that a "finish" works. # This is almost but not quite the same as "call struct funcs". @@ -425,7 +425,7 @@ proc test_struct_returns { n } { set test "value foo<n> finished; ${tests}" gdb_test_multiple "p/c" "${test}" { -re "[foo ${n}]\[\r\n\]+${gdb_prompt} $" { - if $finish_value_known { + if {$finish_value_known} { pass "${test}" } else { # This contradicts the above claim that GDB didn't @@ -435,7 +435,7 @@ proc test_struct_returns { n } { } -re "[zed ${n}]\[\r\n\]+${gdb_prompt} $" { # The value didn't get found. This is "expected". - if $finish_value_known { + if {$finish_value_known} { # This contradicts the above claim that GDB did # know the location of the return-value. fail "${test}" |