[pushed] Run gdb.base/catch-fork-static.exp on remote target boards
Commit Message
Another case of a stale check. We support following forks in the
remote protocol nowadays.
gdb/testsuite/ChangeLog:
2017-10-12 Pedro Alves <palves@redhat.com>
Simon Marchi <simon.marchi@polymtl.ca>
* gdb.base/catch-fork-static.exp: No longer skip on is_remote
target boards.
---
gdb/testsuite/ChangeLog | 6 ++++++
gdb/testsuite/gdb.base/catch-fork-static.exp | 4 ----
2 files changed, 6 insertions(+), 4 deletions(-)
@@ -1,6 +1,12 @@
2017-10-12 Pedro Alves <palves@redhat.com>
Simon Marchi <simon.marchi@polymtl.ca>
+ * gdb.base/catch-fork-static.exp: No longer skip on is_remote
+ target boards.
+
+2017-10-12 Pedro Alves <palves@redhat.com>
+ Simon Marchi <simon.marchi@polymtl.ca>
+
* gdb.base/checkpoint.exp: Don't check is_remote or isnative.
Instead skip if there's any gdb_protocol set.
@@ -21,10 +21,6 @@
# ld.so probes before reaching main, and ptrace flags were set then. But a
# static executable would just keep running and never catch the fork.
-if { [is_remote target] || ![isnative] } then {
- continue
-}
-
# Until "catch fork" is implemented on other targets...
#
if { ![istarget "*-*-linux*"] && ![istarget "*-*-openbsd*"] } then {