From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gregory@heytings.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: add load-libthread-db-quietly option
Date: Mon, 3 Mar 2025 11:31:47 -0500 [thread overview]
Message-ID: <117200f3-59f6-41d1-91ba-abc9089a1734@simark.ca> (raw)
In-Reply-To: <86bjuiktq9.fsf@gnu.org>
On 3/3/25 10:40 AM, Eli Zaretskii wrote:
>> Date: Mon, 3 Mar 2025 09:59:25 -0500
>> Cc: gdb-patches@sourceware.org
>> From: Simon Marchi <simark@simark.ca>
>>
>> People ask us to make it possible to turn this or that message on and
>> off all the time. The proposed command, "set
>> load-libthread-db-quietly", is very specific to that use case. Could we
>> add perhaps a prefix command (or find an existing appropriate one) that
>> would allow us to easily add more such knobs? I'm thinking of something
>> like (maybe not a good name, but just for the example):
>>
>> (gdb) set message load-libthread-db on/off
>
> Sure, why not. But we'd need some infrastructure for each command to
> be able to determine whether it was asked to be quiet, won't we?
I'm not saying we need special infrastructure in the code to handle
this, but just to regroup similar settings under the same prefix, to
keep them together and consistent.
Simon
prev parent reply other threads:[~2025-03-03 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 10:39 Gregory Heytings
2025-03-01 11:46 ` Eli Zaretskii
2025-03-01 12:00 ` Gregory Heytings
2025-03-01 14:10 ` Eli Zaretskii
2025-03-03 14:59 ` Simon Marchi
2025-03-03 15:04 ` Gregory Heytings
2025-03-03 15:26 ` Simon Marchi
2025-03-03 15:58 ` Gregory Heytings
2025-03-26 16:15 ` Tom Tromey
2025-03-26 16:38 ` Gregory Heytings
2025-03-03 15:40 ` Eli Zaretskii
2025-03-03 16:31 ` Simon Marchi [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=117200f3-59f6-41d1-91ba-abc9089a1734@simark.ca \
--to=simark@simark.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gregory@heytings.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