Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: add load-libthread-db-quietly option
Date: Mon, 3 Mar 2025 10:26:13 -0500	[thread overview]
Message-ID: <6adc8d6d-eb2c-41b5-af60-ee3191720ee2@simark.ca> (raw)
In-Reply-To: <121e13947648576b7158@heytings.org>

On 3/3/25 10:04 AM, Gregory Heytings wrote:
> 
>>
>> 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.
>>
> 
> Indeed.
> 
>>
>> 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
>>
> 
> Would
> 
> set print load-libthread-db on/off
> 
> be better?
> 

I initially thought it wouldn't be a good idea because I thought that
"set/show print" only contained options regarding the "print" command,
which is not the same thing as printing or not printing messages.  But
it is used for tweaking messages already.  I see:

set print symbol-loading -- Set printing of symbol loading messages.
set print thread-events -- Set printing of thread events (such as thread start and exit).
set print inferior-events -- Set printing of inferior events (such as inferior start and exit).

So, unless there is a better place for this type of commands that I
don't know about, I think "set print" would be fine.

Simon

  reply	other threads:[~2025-03-03 15:26 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 [this message]
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

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=6adc8d6d-eb2c-41b5-af60-ee3191720ee2@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