[2/6] gdb.base/foll-fork.exp: remove gating based on target triplet

Message ID 20210910205402.3853607-2-simon.marchi@efficios.com
State New
Headers show
  • [1/6] gdb.base/foll-fork.exp: remove DUPLICATEs
Related show

Commit Message

Tom de Vries via Gdb-patches Sept. 10, 2021, 8:53 p.m.
It looks like this test has some code to check at runtime the support of
fork handling of the target (see check_fork_catchpoints).  So, it seems
to me that the check based on target triplet at the beginning of the
test is not needed.  This kind of gating is generally not desirable,
because we wouldn't think of updating it when adding fork support to a
target.  For example, FreeBSD supports fork, but it wasn't listed here.

Change-Id: I6b55f2298edae6b37c3681fb8633d8ea1b5aabee
 gdb/testsuite/gdb.base/foll-fork.exp | 7 -------
 1 file changed, 7 deletions(-)



diff --git a/gdb/testsuite/gdb.base/foll-fork.exp b/gdb/testsuite/gdb.base/foll-fork.exp
index f777f2bda35..e6e84bd3bc0 100644
--- a/gdb/testsuite/gdb.base/foll-fork.exp
+++ b/gdb/testsuite/gdb.base/foll-fork.exp
@@ -13,13 +13,6 @@ 
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
-# Until "set follow-fork-mode" and "catch fork" are implemented on
-# other targets...
-if { ![istarget "*-*-linux*"] && ![istarget "*-*-openbsd*"] } then {
-    continue
 # Test relies on checking follow-fork output. Do not run if gdb debug is
 # enabled as it will be redirected to the log.
 if [gdb_debug_enabled] {