* 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:
parent
8d65888a44
commit
6b0b0a9efb
|
@ -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>
|
2001-05-10 Elena Zannoni <ezannoni@redhat.com>
|
||||||
|
|
||||||
* gdb.base/completion.exp: Revamp test. Make it execute on all
|
* gdb.base/completion.exp: Revamp test. Make it execute on all
|
||||||
|
|
|
@ -77,10 +77,17 @@ proc finish_void { } {
|
||||||
gdb_test "continue" "Breakpoint.* void_func.*" \
|
gdb_test "continue" "Breakpoint.* void_func.*" \
|
||||||
"continue to void_func"
|
"continue to void_func"
|
||||||
send_gdb "finish\n"
|
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 {
|
gdb_expect {
|
||||||
-re ".*void_checkpoint.*$gdb_prompt $" {
|
-re ".*void_checkpoint.*$gdb_prompt $" {
|
||||||
pass "finish from void_func"
|
pass "finish from void_func"
|
||||||
}
|
}
|
||||||
|
-re ".*call to void_func.*$gdb_prompt $" {
|
||||||
|
pass "finish from void_func"
|
||||||
|
}
|
||||||
-re ".*$gdb_prompt $" {
|
-re ".*$gdb_prompt $" {
|
||||||
fail "finish from void_func"
|
fail "finish from void_func"
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue