From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [pushed] Fix --help output
Date: Mon, 22 Dec 2025 11:02:00 -0700 [thread overview]
Message-ID: <20251222180200.3325246-1-tom@tromey.com> (raw)
In commit 9e69a2e127940cc5, which introduced "command" styling, I
accidentally made gdb's --help output mention the "stream" command,
rather than the "help" command.
While doing this I also found a spot where --help output was
incorrectly formatted. This patch fixes this as well.
I'm going to backport this to the gdb-17 branch as well.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33737
---
gdb/main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gdb/main.c b/gdb/main.c
index e4da715134b..93ec9dbc1f2 100644
--- a/gdb/main.c
+++ b/gdb/main.c
@@ -1436,8 +1436,8 @@ This is the GNU debugger. Usage:\n\n\
gdb_puts (_("\
Selection of debuggee and its files:\n\n\
--args Arguments after executable-file are passed to inferior.\n\
- --no-escape-args Like --args, but arguments are not escaped.\n \
- --core=COREFILE Analyze the core dump COREFILE.\n \
+ --no-escape-args Like --args, but arguments are not escaped.\n\
+ --core=COREFILE Analyze the core dump COREFILE.\n\
--exec=EXECFILE Use EXECFILE as the executable.\n\
--pid=PID Attach to running process PID.\n\
--directory=DIR Search for source files in DIR.\n\
@@ -1544,7 +1544,7 @@ At startup, GDB reads the following init files and executes their commands:\n\
For more information, type \"%ps\" from within GDB, or consult the\n\
GDB manual (available as on-line info or a printed manual).\n\
"),
- styled_string (command_style.style (), "stream"));
+ styled_string (command_style.style (), "help"));
if (REPORT_BUGS_TO[0] && stream == gdb_stdout)
gdb_printf (stream, _("\n\
Report bugs to %ps.\n\
--
2.49.0
next reply other threads:[~2025-12-22 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 18:02 Tom Tromey [this message]
2025-12-22 18:18 ` Tom Tromey
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=20251222180200.3325246-1-tom@tromey.com \
--to=tom@tromey.com \
--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