From: Gregory Heytings <gregory@heytings.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] gdb: add load-libthread-db-quietly option
Date: Sat, 01 Mar 2025 10:39:06 +0000 [thread overview]
Message-ID: <d3de7625e44e7592198a@heytings.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
In line with the Unix tradition in which no messages are displayed when no
error happens, I suggest the attached patch, with which users could "set
load-libthread-db-quietly off" in their .gdbinit file.
Thanks.
[-- Attachment #2: gdb-add-load-libthread-db-quietly-option.patch --]
[-- Type: text/x-diff, Size: 3786 bytes --]
From 472624cf3044b1351f164c308eb9cea5b7351333 Mon Sep 17 00:00:00 2001
From: Gregory Heytings <gregory@heytings.org>
Date: Sat, 1 Mar 2025 10:27:18 +0000
Subject: [PATCH] gdb: add load-libthread-db-quietly option
Setting that option disables the "Thread debugging using libthread_db
enabled" and "Using host libthread_db library..." messages.
---
gdb/doc/gdb.texinfo | 7 +++++++
gdb/linux-thread-db.c | 29 ++++++++++++++++++++++++++---
2 files changed, 33 insertions(+), 3 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 29c0118dda2..036150e423e 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4073,6 +4073,13 @@ only on some platforms.
@item show libthread-db-search-path
Display current libthread_db search path.
+@kindex set load-libthread-db-quietly
+@kindex show load-libthread-db-quietly
+@item set load-libthread-db-quietly
+@itemx show load-libthread-db-quietly
+Turns on or off display of messages when @code{libthread_db} is loaded.
+The default is @code{off}.
+
@kindex set debug libthread-db
@kindex show debug libthread-db
@cindex debugging @code{libthread_db}
diff --git a/gdb/linux-thread-db.c b/gdb/linux-thread-db.c
index 9d84187a9ad..d042d51c5fd 100644
--- a/gdb/linux-thread-db.c
+++ b/gdb/linux-thread-db.c
@@ -120,6 +120,9 @@ static bool auto_load_thread_db = true;
by the "maintenance set check-libthread-db" command. */
static bool check_thread_db_on_load = false;
+/* Set to true if loading libthread_db happens quietly. */
+static bool load_libthread_db_quiet = false;
+
/* "show" command for the auto_load_thread_db configuration variable. */
static void
@@ -150,6 +153,15 @@ show_libthread_db_debug (struct ui_file *file, int from_tty,
gdb_printf (file, _("libthread-db debugging is %s.\n"), value);
}
+/* "show" command for the load_libthread_db_quiet configuration variable. */
+
+static void
+show_load_libthread_db_quiet (struct ui_file *file, int from_tty,
+ struct cmd_list_element *c, const char* value)
+{
+ gdb_printf (file, _("Loading libthread_db quietly is %s.\n"), value);
+}
+
/* If we're running on GNU/Linux, we must explicitly attach to any new
threads. */
@@ -936,7 +948,8 @@ try_thread_db_load_1 (struct thread_db_info *info)
return false;
}
- gdb_printf (_("[Thread debugging using libthread_db enabled]\n"));
+ if (!load_libthread_db_quiet)
+ gdb_printf (_("[Thread debugging using libthread_db enabled]\n"));
if (!libthread_db_search_path.empty () || libthread_db_debug)
{
@@ -946,8 +959,9 @@ try_thread_db_load_1 (struct thread_db_info *info)
if (library == NULL)
library = LIBTHREAD_DB_SO;
- gdb_printf (_("Using host libthread_db library \"%ps\".\n"),
- styled_string (file_name_style.style (), library));
+ if (!load_libthread_db_quiet)
+ gdb_printf (_("Using host libthread_db library \"%ps\".\n"),
+ styled_string (file_name_style.style (), library));
}
/* The thread library was detected. Activate the thread_db target
@@ -2050,6 +2064,15 @@ as they are loaded."),
&maintenance_set_cmdlist,
&maintenance_show_cmdlist);
+ add_setshow_boolean_cmd ("load-libthread-db-quietly", class_support,
+ &load_libthread_db_quiet, _("\
+Set whether GDB should load libthread_db quietly."), _("\
+Show whether GDB should start load libthread_db quietly."), _("\
+If enabled, GDB will load libthread_db without printing messages."),
+ NULL,
+ show_load_libthread_db_quiet,
+ &setlist, &showlist);
+
/* Add ourselves to objfile event chain. */
gdb::observers::new_objfile.attach (thread_db_new_objfile, "linux-thread-db");
--
2.39.2
next reply other threads:[~2025-03-01 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 10:39 Gregory Heytings [this message]
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
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=d3de7625e44e7592198a@heytings.org \
--to=gregory@heytings.org \
--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