gdb/testsuite/gdb.base/step-test.exp

   1 # Copyright (C) 1997, 1998, 1999 Free Software Foundation, Inc.
   2
   3 # This program is free software; you can redistribute it and/or modify
   4 # it under the terms of the GNU General Public License as published by
   5 # the Free Software Foundation; either version 2 of the License, or
   6 # (at your option) any later version.
   7 #
   8 # This program is distributed in the hope that it will be useful,
   9 # but WITHOUT ANY WARRANTY; without even the implied warranty of
  10 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  11 # GNU General Public License for more details.
  12 #
  13 # You should have received a copy of the GNU General Public License
  14 # along with this program; if not, write to the Free Software
  15 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  */
  16
  17 # Please email any bugs, comments, and/or additions to this file to:
  18 # bug-gdb@prep.ai.mit.edu
  19
  20 # use this to debug:
  21 #
  22 #log_user 1
  23
  24 # step-test.exp -- Expect script to test stepping in gdb
  25
  26 if $tracelevel then {
  27     strace $tracelevel
  28 }
  29
  30 set testfile step-test
  31 set srcfile ${srcdir}/${subdir}/${testfile}.c
  32 set binfile ${objdir}/${subdir}/${testfile}
  33
  34 remote_exec build "rm -f ${binfile}"
  35 if { [gdb_compile "${srcfile}" "${binfile}" executable {debug}] != "" } {
  36      gdb_suppress_entire_file "Testcase compile failed, so all tests in this file will automatically fail."
  37 }
  38
  39 gdb_exit
  40 gdb_start
  41 gdb_reinitialize_dir $srcdir/$subdir
  42 gdb_load ${binfile}
  43
  44 if ![runto_main] then {
  45    fail "Can't run to main"
  46    return 0
  47 }
  48
  49 # Set a breakpoint at line 45, if stepi then finish fails, we would
  50 # run to the end of the program, which would mess up the rest of the tests.
  51
  52 # Vanilla step/next
  53 #
  54 gdb_test "next" ".*${decimal}.*x = 1;.*" "next 1"
  55 gdb_test "step" ".*${decimal}.*y = 2;.*" "step 1"
  56
  57 # With count
  58 #
  59 gdb_test "next 2" ".*${decimal}.*w = w.*2;.*" "next 2"
  60 gdb_test "step 3" ".*${decimal}.*z = z.*5;.*" "step 3"
  61 gdb_test "next" ".*${decimal}.*callee.*OVER.*" "next 3"
  62
  63 # Step over call
  64 #
  65 gdb_test "next" ".*${decimal}.*callee.*INTO.*" "next over"
  66
  67 # Step into call
  68 #
  69 gdb_test "step" ".*${decimal}.*glob.*"   "step into"
  70
  71 # Step out of call
  72 #
  73 # I wonder if this is really portable.  Are there any caller-saves
  74 # platforms, on which `finish' will return you to some kind of pop
  75 # instruction, which is attributed to the line containing the function
  76 # call?
  77 gdb_test "finish" ".*${decimal}.*a.*5.*= a.*3.*" "step out"
  78
  79 ### Testing nexti and stepi.
  80 ###
  81 ### test_i NAME COMMAND HERE THERE
  82 ###
  83 ### Send COMMAND to gdb over and over, while the output matches the
  84 ### regexp HERE, followed by the gdb prompt.  Pass if the output
  85 ### eventually matches the regexp THERE, followed by the gdb prompt;
  86 ### fail if we have to iterate more than a hundred times, we time out
  87 ### talking to gdb, or we get output which is neither HERE nor THERE.  :)
  88 ###
  89 ### Use NAME as the name of the test.
  90 ###
  91 ### The exact regexps used are "$HERE.*$gdb_prompt $"
  92 ###                        and "$THERE.*$gdb_prompt $"
  93 ###
  94 proc test_i {name command here there} {
  95     global gdb_prompt
  96
  97     set i 0
  98     while 1 {
  99         send_gdb "${command}\n"
 100         gdb_expect {
 101             -re "$here.*$gdb_prompt $" {
 102                 # Okay, we're still on the same line.  Just step again.
 103             }
 104             -re "$there.*$gdb_prompt $" {
 105                 # We've reached the next line.  Rah.
 106                 pass "$name"
 107                 return
 108             }
 109             -re "$gdb_prompt $" {
 110                 # We got something else.  Fail.
 111                 fail "$name"
 112                 return
 113             }
 114             timeout {
 115                 fail "$name (timeout)"
 116                 return
 117             }
 118         }
 119
 120         # Have we gone for too many steps without seeing any progress?
 121         if {[incr i] >= 100} {
 122             fail "$name (no progress after 100 steps)"
 123             return
 124         }
 125     }
 126 }
 127
 128 test_i "stepi to next line" "stepi" \
 129        ".*${decimal}.*a.*5.* = a.*3" \
 130        ".*${decimal}.*callee.*STEPI"
 131 test_i "stepi into function" "stepi" \
 132        ".*${decimal}.*callee.*STEPI" \
 133        ".*callee \\(\\) at .*step-test\\.c"
 134 # Have to be careful here, if the finish does not work,
 135 # then we may run to the end of the program, which
 136 # will cause erroneous failures in the rest of the tests
 137
 138 send_gdb "finish\n"
 139 gdb_expect {
 140   -re ".*(Program received|Program exited).*$gdb_prompt $" {
 141     puts "*** Matched Program recieved"
 142     # Oops... We ran to the end of the program...  Better reset
 143     if {![runto_main]} then {
 144       fail "Can't run to main"
 145       return 0
 146     }
 147     if {![runto step-test.c:45]} {
 148       fail "Can't run to line 45"
 149       return 0
 150     }
 151     fail "stepi: finish call"
 152   }
 153   -re ".*${decimal}.*callee.*NEXTI.*$gdb_prompt $" {
 154     puts "*** Matched success..."
 155     pass "stepi: finish call"
 156   }
 157   -re "$gdb_prompt $" {
 158     # We got something else.  Fail.
 159     fail "stepi: finish call"
 160     return
 161   }
 162   timeout {
 163     fail "stepi: finish call"
 164     return
 165   }
 166 }
 167
 168 test_i "nexti over function" "nexti" \
 169        ".*${decimal}.*callee.*NEXTI" \
 170        ".*${decimal}.*y = w \\+ z;"
 171
 172 # On some platforms, if we try to step into a function call that
 173 # passes a large structure by value, then we actually end up stepping
 174 # into memcpy, bcopy, or some such --- GCC emits the call to pass the
 175 # argument.  Opinion is bitterly divided about whether this is the
 176 # right behavior for GDB or not, but we'll catch it here, so folks
 177 # won't forget about it.
 178
 179 send_gdb "break [gdb_get_line_number "step-test.exp: large struct by value"]\n"
 180 gdb_test "continue" \
 181          ".*Breakpoint ${decimal},.*large_struct_by_value.*" \
 182          "run to pass large struct"
 183 gdb_test "step" \
 184          ".*step-test.exp: arrive here 1.*" \
 185          "large struct by value"
 186
 187 gdb_continue_to_end "step-test.exp"
 188
 189 return 0