From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb, configure: Add disable-formats option for configure
Date: Fri, 27 Sep 2024 09:05:06 +0300 [thread overview]
Message-ID: <8634llaay5.fsf@gnu.org> (raw)
In-Reply-To: <cbe2898c-2fde-4c64-be7c-1063ecd7ad0b@redhat.com> (message from Guinevere Larsen on Thu, 26 Sep 2024 18:03:05 -0300)
> Date: Thu, 26 Sep 2024 18:03:05 -0300
> Cc: gdb-patches@sourceware.org
> From: Guinevere Larsen <guinevere@redhat.com>
>
> > My point was that the manual doesn't clarify these issues. It left me
> > confused.
> >
> >>> Maybe I'm confused, but if I am, it means we lack some important
> >>> information in the manual which would clarify this.
> >> Maybe more clarity would be helpful, but I don't think these issues have
> >> to do with my patch itself, so I think this should be further
> >> improvement for documentation rather than having to fix it in this patch.
> > You may be right, but without clarifying this whole issue I cannot
> > decide whether your additions about this are okay or not. So I think
> > we have no choice but to clarify those other aspects together with
> > this review, even if just in principle.
> I hope I clarified enough in this email to allow you to judge my changes
> on their own, and a later unrelated patch can fill in the missing
> information, since the changes really aren't related to enable-targets
> and it was my mistake to parse them there instead of just seeing which
> tdep files are compiled in and need a file format.
Unfortunately, I'm still in the dark here. I'd appreciate if you or
someone else who understands the way we deal with targets in all the 3
scenarios -- native debugging, cross-debugging, remote debugging --
could explain how this stuff works (and perhaps how it should work
ideally, if what we have is not ideal/correct), and then we could take
it from there.
We could, of course, just go with your changes disregarding these
larger issues, but I think clarifying them will also help us
understand better this new feature and make sure it is designed and
implemented correctly.
OTOH, if I'm the only one who doesn't fully understand this stuff, and
everyone else agrees with the suggested changes as they are, feel free
to ignore me.
next prev parent reply other threads:[~2024-09-27 6:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 17:53 Guinevere Larsen
2024-09-26 5:49 ` Eli Zaretskii
2024-09-26 18:16 ` Guinevere Larsen
2024-09-26 18:35 ` Eli Zaretskii
2024-09-26 21:03 ` Guinevere Larsen
2024-09-27 6:05 ` Eli Zaretskii [this message]
2024-10-02 13:25 ` Andrew Burgess
2024-10-02 14:15 ` Eli Zaretskii
2024-10-04 14:26 ` Andrew Burgess
2024-10-04 14:45 ` Eli Zaretskii
2024-10-07 18:30 ` Guinevere Larsen
2024-10-07 19:17 ` Eli Zaretskii
2024-10-07 19:58 ` Guinevere Larsen
2024-10-08 11:44 ` Eli Zaretskii
2024-10-08 13:03 ` Guinevere Larsen
2024-10-08 13:21 ` Eli Zaretskii
2024-10-10 14:45 ` Guinevere Larsen
2024-10-10 16:10 ` Andrew Burgess
2024-09-26 19:18 ` Tom Tromey
2024-09-26 19:49 ` Guinevere Larsen
2024-09-27 18:01 ` Tom Tromey
2024-10-02 13:56 ` Andrew Burgess
2024-10-02 20:37 ` Guinevere Larsen
2024-10-03 10:15 ` Andrew Burgess
2024-10-04 14:49 ` Andrew Burgess
2024-10-10 20:18 ` Guinevere Larsen
2024-10-16 10:50 ` Andrew Burgess
2024-10-16 21:00 ` Guinevere Larsen
2024-10-17 19:43 ` Tom Tromey
2024-10-17 19:48 ` Guinevere Larsen
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=8634llaay5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.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