Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: aburgess@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb, configure: Add disable-formats option for configure
Date: Tue, 08 Oct 2024 16:21:42 +0300	[thread overview]
Message-ID: <86msjespax.fsf@gnu.org> (raw)
In-Reply-To: <49074401-6680-4ed1-9263-c098053f8ed9@redhat.com> (message from Guinevere Larsen on Tue, 8 Oct 2024 10:03:58 -0300)

> Date: Tue, 8 Oct 2024 10:03:58 -0300
> Cc: aburgess@redhat.com, gdb-patches@sourceware.org
> From: Guinevere Larsen <guinevere@redhat.com>
> 
> Ultimately, this is a feature for advanced users who have deep domain 
> knowledge on the systems they expect to handle, and similar to how, even 
> with the update on the --target and --enable-targets documentation, I 
> wouldn't expect every single target triplet supported by GDB to be 
> listed in the documentation, I don't think we should list what formats 
> are recommended for each target.
> 
> I can change the first paragraph of the description to read as follows:
>    Configure GDB to only be be able to read selected file formats. The
>    special value "all" causes all file formats to be compiled in, and is 
> the
>    the default behavior of the option. If you are unsure of which options
>    you will need for your debugging sessions, we recommend that you
>    not make use of this function. The possible options are:
> 
> <list of options as sent in previous email>

Maybe this is better.

I'm worried by the fact that I'm the only one talking to you about
this: maybe there's no problem at all, and I'm the only one confused.
In that case, apologies for wasting your time.

  reply	other threads:[~2024-10-08 13:22 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
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 [this message]
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=86msjespax.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --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