From: Tom Tromey <tom@tromey.com>
To: Simon Farre via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Farre <simon.farre.cx@gmail.com>,
tom@tromey.com, aburgess@redhat.com
Subject: Re: [PATCH v2] gdb/dap - Add support for additional target types
Date: Tue, 20 Jun 2023 08:02:45 -0600 [thread overview]
Message-ID: <87wmzy2pve.fsf@tromey.com> (raw)
In-Reply-To: <20230620100017.229708-1-simon.farre.cx@gmail.com> (Simon Farre via Gdb-patches's message of "Tue, 20 Jun 2023 12:00:17 +0200")
>>>>> "Simon" == Simon Farre via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> After discussion with Tom and Andrew we decided that the best approach
Simon> is the simple one - make the "target" field contain a string that
Simon> performs the desired command.
Simon> So for instance "extended-remote 127.0.0.1:50505" or "remote foohost"
Simon> etc.
I think this will require a patch to the test suite, either in
dap_target_remote or in its caller in remote-dap.exp.
It also needs an update to the documentation.
Tom
next prev parent reply other threads:[~2023-06-20 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 10:00 Simon Farre
2023-06-20 14:02 ` Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-13 12:06 Simon Farre
2023-06-13 18:32 ` Tom Tromey
2023-06-14 10:54 ` Simon Farre
2023-06-14 11:56 ` Andrew Burgess
2023-06-14 12:01 ` Simon Farre
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=87wmzy2pve.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.farre.cx@gmail.com \
/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).