PATCH/testsuite: guard test in ending-run.exp with stdio check

[Daniel Jacobowitz]

If we don't have inferior I/O, we won't see the program's output when we
continue.  Committed as obvious.  Yet another failure I noticed when testing
my unreviewed gdbserver.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

2002-02-10  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.base/ending-run.exp: Guard "cont" test with
	gdb_skip_stdio_test.

Index: testsuite/gdb.base/ending-run.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/ending-run.exp,v
retrieving revision 1.11
diff -u -p -r1.11 ending-run.exp
--- ending-run.exp	2002/01/21 18:46:33	1.11
+++ ending-run.exp	2002/02/10 16:48:46
@@ -129,7 +129,11 @@ gdb_expect {
 # See if we can step out with control.  The "1 2 3" stuff
 # is output from the program.
 #
-gdb_test "cont" ".*1 2 7 14 23 34 47 62 79.*Breakpoint.*31.*"
+if ![gdb_skip_stdio_test "cont"] {
+    gdb_test "cont" ".*1 2 7 14 23 34 47 62 79.*Breakpoint.*31.*"
+} else {
+    gdb_test "cont" ".*Breakpoint.*31.*"
+}
 
 if ![gdb_skip_stdio_test "Step to return"] {
     gdb_test "next" ".*Goodbye!.*32.*" \