From: Simon Farre <simon.farre.cx@gmail.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb/dap - Add support for additional target types
Date: Wed, 14 Jun 2023 14:01:47 +0200 [thread overview]
Message-ID: <53a74d37-1f9f-0cb5-83c0-9427fe8c7061@gmail.com> (raw)
In-Reply-To: <87mt12w939.fsf@redhat.com>
> I know this change was focused on remote/extended-remote, but just to
> backup what Tom is suggesting, 'target sim' takes an arbitrary set of
> options, which can vary depending on which simulator is being invoked,
> there's no one single set of arguments. Thus just passing any argument
> string through from Python to GDB will be best for that target.
>
> Thanks,
> Andrew
>
I see. Yeah, I think that settles it then. I'll update the patch just
"streamline" through the target string, as it were. This is also closer
to the initial implementation I had tested on my machine.
Thanks!
Simon
next prev parent reply other threads:[~2023-06-14 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-06-20 10:00 Simon Farre
2023-06-20 14:02 ` Tom Tromey
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=53a74d37-1f9f-0cb5-83c0-9427fe8c7061@gmail.com \
--to=simon.farre.cx@gmail.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@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).