public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.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	[thread overview]
Message-ID: <bug-29736-4717-5z2kfSoIin@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29736-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29736

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> V. build == target == localhost, host == remote
> 
> 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.
> 
> 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.
> 

I've come to the conclusion that these host boards only make sense in
combination with one of the target boards that force gdbserver.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2022-11-03 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 14:48 [Bug testsuite/29736] New: " vries at gcc dot gnu.org
2022-11-03 21:10 ` vries at gcc dot gnu.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29736-4717-5z2kfSoIin@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).