OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* gdb.base/finish.exp (finish_void): Allow "finish" command to 

stop on the call statement as well as the statement after the
	call.
This commit is contained in:
Kevin Buettner 2001-05-22 00:25:27 +00:00
parent 8d65888a44
commit 6b0b0a9efb
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,9 @@
2001-05-21 Kevin Buettner <kevinb@redhat.com>
* gdb.base/finish.exp (finish_void): Allow "finish" command to
stop on the call statement as well as the statement after the
call.
2001-05-10 Elena Zannoni <ezannoni@redhat.com>
* gdb.base/completion.exp: Revamp test. Make it execute on all

7
gdb/testsuite/gdb.base/finish.exp
View File

@ -77,10 +77,17 @@ proc finish_void { } {
gdb_test "continue" "Breakpoint.* void_func.*" \
"continue to void_func"
send_gdb "finish\n"
# Some architectures will have one or more instructions after the
# call instruction which still is part of the call sequence, so we
# must be prepared for a "finish" to show us the void_func call
# again as well as the statement after.
gdb_expect {
-re ".*void_checkpoint.*$gdb_prompt $" {
pass "finish from void_func"
}
-re ".*call to void_func.*$gdb_prompt $" {
pass "finish from void_func"
}
-re ".*$gdb_prompt $" {
fail "finish from void_func"
}