diff options
author | Kevin Buettner <kevinb@redhat.com> | 2001-05-22 00:25:27 +0000 |
---|---|---|
committer | Kevin Buettner <kevinb@redhat.com> | 2001-05-22 00:25:27 +0000 |
commit | 6b0b0a9efbc3f40fb6277e36b573b26ed0476b6b (patch) | |
tree | 37d88c738cb91f44721e53d5da4323b895791bc4 /gdb/testsuite/gdb.base/finish.exp | |
parent | 8d65888a44248188564eef092fb32fbac74a464a (diff) | |
download | gdb-6b0b0a9efbc3f40fb6277e36b573b26ed0476b6b.zip gdb-6b0b0a9efbc3f40fb6277e36b573b26ed0476b6b.tar.gz gdb-6b0b0a9efbc3f40fb6277e36b573b26ed0476b6b.tar.bz2 |
* gdb.base/finish.exp (finish_void): Allow "finish" command to
stop on the call statement as well as the statement after the
call.
Diffstat (limited to 'gdb/testsuite/gdb.base/finish.exp')
-rw-r--r-- | gdb/testsuite/gdb.base/finish.exp | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.base/finish.exp b/gdb/testsuite/gdb.base/finish.exp index abb35ed..3e2c69f 100644 --- a/gdb/testsuite/gdb.base/finish.exp +++ b/gdb/testsuite/gdb.base/finish.exp @@ -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" } |