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

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:
Pedro Alves 2015-07-29 11:09:37 +01:00
parent 23ffc893f5
commit 12264a451d
2 changed files with 5 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/testsuite/ChangeLog
View File

@ -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

15
gdb/testsuite/gdb.base/restore.exp
View File

@ -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