From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 613C83858404; Thu, 3 Nov 2022 21:10:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 613C83858404 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1667509809; bh=nKyCoqnvAIb2W5K95DAbVsBoPWbWDnjxLVWV/ita990=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vEb9wpluK61ZC6njMtrzqjSzEGO2Sl6yD8PQF1+EmcD42k8gozWtKriuoPFEHeofZ RakOdA7fdpchyBDfYboqvufvPIrgCFXdOUPDM9rF2kosS6DOw+NMGv+F0ICdy/6c6s LMp8zRvks7CKhgLqSsLKRNfuAFgY6mUvz6JqgAqw= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/29736] [gdb/testsuite] Review of remote host/target boards in gdb/testsuite/boards Date: Thu, 03 Nov 2022 21:10:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29736 --- Comment #1 from Tom de Vries --- (In reply to Tom de Vries from comment #0) > V. build =3D=3D target =3D=3D localhost, host =3D=3D remote >=20 > There are two host boards, local-remote-host-notty.exp and > local-remote-host.exp that test using a remote host, accessing the remote > host using ssh. Again, note that the remote host also happens to be > localhost, but as far as dejagnu is considered it is a distinct machine. >=20 > Here we don't force execs to be launched using gdbserver, which looks > somewhat strange, because also here if gdb is launching an exec, it's > running on the host, not the target. We can get away with this because > under the hood the remote host and the local target are the same machine, > but AFAIU, we're not testing what we're supposed to test. >=20 I've come to the conclusion that these host boards only make sense in combination with one of the target boards that force gdbserver. --=20 You are receiving this mail because: You are on the CC list for the bug.=