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 <palves@redhat.com> * gdb.base/restore.exp (restore_tests): Use gdb_continue_to_end.
This commit is contained in:
parent
23ffc893f5
commit
12264a451d
|
@ -1,3 +1,7 @@
|
|||
2015-07-29 Pedro Alves <palves@redhat.com>
|
||||
|
||||
* gdb.base/restore.exp (restore_tests): Use gdb_continue_to_end.
|
||||
|
||||
2015-07-29 Pedro Alves <palves@redhat.com>
|
||||
|
||||
* gdb.base/call-signal-resume.exp: Remove check for
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue