[PATCH] gdbserver: Don't try to reopen stdio just quit

[Mark Wielaard <mark@klomp.org>]

The testsuite sometimes leaves around gdbserver processes that are
stuck in a loop trying to reopen stdio, which will not work. Once the
write side of the pipe is gone it won't come back because it cannot be
reconnected to another process.

This requires the buildbot to killall gdbserver after running check-gdb.

Add an extra check for remote_connection_is_stdio () in captured_main
to quit in the gdbserver was started through a pipe with - as comm
and stdio as event source is gone.
---
 gdbserver/server.cc | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/gdbserver/server.cc b/gdbserver/server.cc
index 6f9d2a85609b..c22aa98854cc 100644
--- a/gdbserver/server.cc
+++ b/gdbserver/server.cc
@@ -4382,13 +4382,18 @@ captured_main (int argc, char *argv[])
 
 	      - If --once was specified, we're done.
 
+	      - If the remote connection was stdio it is now closed
+		and it will not reopen.
+
 	      - If not in extended-remote mode, and we're no longer
 		debugging anything, simply exit: GDB has disconnected
 		after processing the last process exit.
 
 	      - Otherwise, close the connection and reopen it at the
 		top of the loop.  */
-	  if (run_once || (!extended_protocol && !target_running ()))
+	  if (run_once
+	      || remote_connection_is_stdio ()
+	      || (!extended_protocol && !target_running ()))
 	    throw_quit ("Quit");
 
 	  fprintf (stderr,
-- 
2.45.2