Don't run gdb.gdb/ selftests if use_gdb_stub is true
authorPedro Alves <palves@redhat.com>
Thu, 12 Oct 2017 17:29:21 +0000 (18:29 +0100)
committerPedro Alves <palves@redhat.com>
Fri, 13 Oct 2017 16:26:04 +0000 (17:26 +0100)
commitdad0c6d2f7410d3b451800f856f3c6818303c316
tree089709722baac5ca3b10f345461149ea4a73822e
parent8b0553c18f0dc63ab0ae930f2e8eed2bce4cd32c
Don't run gdb.gdb/ selftests if use_gdb_stub is true

If we make the native-gdbserver board be !is_remote, then the few
tests that use the selftest-support.exp routines to debug gdb itself
start running, and fail, with something like:

  Running ..../src/gdb/testsuite/gdb.gdb/selftest.exp ...
  ERROR: tcl error sourcing ..../src/gdb/testsuite/gdb.gdb/selftest.exp.
  ERROR: gdbserver does not support run [....] without extended-remote
      while executing
  "error "gdbserver does not support $command without extended-remote""
      (procedure "gdb_test_multiple" line 25)
      invoked from within
  "gdb_test_multiple "run $INTERNAL_GDBFLAGS" "$description" {
  -re "Starting program.*Breakpoint \[0-9\]+,.*$function \\(\\).* at .*main.c:.*$gdb..."
      (procedure "selftest_setup" line 45)

This commit makes sure those tests continue to be skipped.

gdb/testsuite/ChangeLog:
2017-10-13  Pedro Alves  <palves@redhat.com>

* lib/selftest-support.exp (selftest_setup): Extend comments, and
also skip on stub-like targets.
gdb/testsuite/ChangeLog
gdb/testsuite/lib/selftest-support.exp