From 12264a451d993a0a8635be82bed15618e0f4645f Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Wed, 29 Jul 2015 11:09:37 +0100 Subject: Don't rely on inferior I/O in gdb.base/restore.exp There seems to be no point in relying on stdio here. Simply use gdb_continue_to_end instead. (not removing the printf calls, as the .c file is half generated.) gdb/testsuite/ChangeLog: 2015-07-29 Pedro Alves * gdb.base/restore.exp (restore_tests): Use gdb_continue_to_end. --- gdb/testsuite/gdb.base/restore.exp | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) (limited to 'gdb/testsuite/gdb.base') diff --git a/gdb/testsuite/gdb.base/restore.exp b/gdb/testsuite/gdb.base/restore.exp index a02ba4f..bd9dfbf 100644 --- a/gdb/testsuite/gdb.base/restore.exp +++ b/gdb/testsuite/gdb.base/restore.exp @@ -79,20 +79,7 @@ proc restore_tests { } { } } - if ![gdb_skip_stdio_test "run to completion"] { - send_gdb "continue\n" - - gdb_expect { - -re "exiting" { - pass "run to completion" - } - timeout { - fail "(timeout) run to completion" - } - } - } else { - gdb_test "continue" ".*" "" - } + gdb_continue_to_end "" continue 1 } set prev_timeout $timeout -- cgit v1.1