From: "Jim Blandy" <jimb@red-bean.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: RFA: Fix manual summary of 'info' command
Date: Fri, 01 Feb 2008 22:10:00 -0000 [thread overview]
Message-ID: <8f2776cb0802011410u518ffc08yaa0424105e51a87@mail.gmail.com> (raw)
This is a fix for gdb/2411. Okay to commit?
gdb/doc/ChangeLog:
2008-02-01 Jim Blandy <jimb@red-bean.com>
* gdb.texinfo (Help): Summarize 'info args' correctly.
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.466
diff -u -r1.466 gdb.texinfo
--- gdb/doc/gdb.texinfo 31 Jan 2008 13:38:49 -0000 1.466
+++ gdb/doc/gdb.texinfo 1 Feb 2008 21:58:13 -0000
@@ -1651,7 +1651,7 @@
@kindex i @r{(@code{info})}
@item info
This command (abbreviated @code{i}) is for describing the state of your
-program. For example, you can list the arguments given to your program
+program. For example, you can show the arguments passed to a function
with @code{info args}, list the registers currently in use with @code{info
registers}, or list the breakpoints you have set with @code{info breakpoints}.
You can get a complete list of the @code{info} sub-commands with
next reply other threads:[~2008-02-01 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 22:10 Jim Blandy [this message]
2008-02-02 10:38 ` Eli Zaretskii
2008-02-03 18:56 ` Jim Blandy
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=8f2776cb0802011410u518ffc08yaa0424105e51a87@mail.gmail.com \
--to=jimb@red-bean.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