[PATCH 0/2] Make catch-syscall.exp work with "target remote".

Pedro Alves
2013-09-27T19:22:15Z

Running the pending GDBserver "catch syscall" patch against the
native-gdbserver.exp board ("target remote", instead of the
native-extended-gdbserver.exp board ("target extended-remote") fails
the existing catch-syscall.exp test. These look like problems with
the testsuite, actually independent of the catch syscall support, so I
took a stab at fixing them.

Unfortunately, the first patch regresses testing against the stdio
board. The second patch fixes that. If people are OK with these
patches, I'll swap their order before check in.

Pedro Alves (2):
Make catch-syscall.exp work with "target remote". A.k.a., teach the
testsuite that GDBserver reliably reports program exits.
[GDBserver]: Silence exits if GDB is connected through stdio.

gdb/gdbserver/server.c | 5 ++++-
gdb/gdbserver/target.c | 23 ++++++++++++++++-------
gdb/testsuite/README | 8 ++++++++
gdb/testsuite/boards/native-gdbserver.exp | 1 +
gdb/testsuite/boards/native-stdio-gdbserver.exp | 1 +
gdb/testsuite/lib/gdb.exp | 21 +++++++++++++++------
6 files changed, 45 insertions(+), 14 deletions(-)

--
1.7.11.7