From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: [COMMIT] Add indexing for standard registers, fix GDB name
Date: Fri, 03 Jun 2005 07:14:00 -0000 [thread overview]
Message-ID: <uis0vc3pi.fsf@gnu.org> (raw)
FYI, I've just committed the following patch that deals with 2
problems:
. The standard registers didn't have index entries.
. There was a typo in Annotations Overview node: it used
@value{GDB}.
2005-06-03 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Registers): Add index entries for the standard
registers.
(Frames): Add cross-reference from frame pointer description to
the Registers node.
(Annotations Overview): Fix the reference to GDB name.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.259
retrieving revision 1.260
diff -u -r1.259 -r1.260
--- gdb.texinfo 1 Jun 2005 20:38:44 -0000 1.259
+++ gdb.texinfo 3 Jun 2005 07:09:17 -0000 1.260
@@ -4149,8 +4149,8 @@
stack frame consists of many bytes, each of which has its own address; each
kind of computer has a convention for choosing one byte whose
address serves as the address of the frame. Usually this address is kept
-in a register called the @dfn{frame pointer register} while execution is
-going on in that frame.
+in a register called the @dfn{frame pointer register}
+(@pxref{Registers, $fp}) while execution is going on in that frame.
@cindex frame number
@value{GDBN} assigns numbers to all existing stack frames, starting with
@@ -6128,6 +6128,11 @@
the machine you are using, with or without the initial @samp{$}.
@end table
+@cindex stack pointer register
+@cindex program counter register
+@cindex process status register
+@cindex frame pointer register
+@cindex standard registers
@value{GDBN} has four ``standard'' register names that are available (in
expressions) on most machines---whenever they do not conflict with an
architecture's canonical mnemonics for registers. The register names
@@ -20589,7 +20594,7 @@
@table @code
@kindex set annotate
@item set annotate @var{level}
-The @value{GDB} command @code{set annotate} sets the level of
+The @value{GDBN} command @code{set annotate} sets the level of
annotations to the specified @var{level}.
@item show annotate
reply other threads:[~2005-06-03 7:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=uis0vc3pi.fsf@gnu.org \
--to=eliz@gnu.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