From: Andrew Cagney <ac131313@ges.redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa:doco] Add ``maint print registers''
Date: Fri, 09 Aug 2002 17:07:00 -0000 [thread overview]
Message-ID: <3D545935.8010605@ges.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
Hello,
This adds documentation for the commands:
maint print regiters
maint print raw-registers
maint print cooked-registers
One thing I've noticed in the doco is that it refers to cooked but
cooked is an internal thing explained (or it will be ...) in the
internals document.
ok?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1102 bytes --]
Index: doc/ChangeLog
2002-08-09 Andrew Cagney <cagney@redhat.com>
* gdb.texinfo (Maintenance Commands): Document "maint print
registers", "maint print raw-registers" and "maint print
cooked-registers".
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.108
diff -u -r1.108 gdb.texinfo
--- doc/gdb.texinfo 9 Aug 2002 16:41:25 -0000 1.108
+++ doc/gdb.texinfo 10 Aug 2002 00:04:08 -0000
@@ -14195,6 +14195,18 @@
@end table
+@kindex maint print registers
+@kindex maint print raw-registers
+@kindex maint print cooked-registers
+@item @anchor{maint print registers}maint print registers
+@itemx @anchor{maint print raw-registers}maint print raw-registers
+@itemx @anchor{maint print cooked-registers}maint print cooked-registers
+Print @value{GDBN}'s internal register structure. @samp{maint print
+raw-registers} includes the raw register cache value while @samp{maint
+print cooked-registers} includes the cooked register value.
+
+Takes an optional file parameter.
+
@end table
next reply other threads:[~2002-08-10 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 17:07 Andrew Cagney [this message]
2002-08-11 6:46 ` Eli Zaretskii
2002-08-11 9:40 ` Andrew Cagney
2002-08-12 10:25 ` Eli Zaretskii
2002-08-13 14:33 ` Andrew Cagney
2002-08-14 4:01 ` Eli Zaretskii
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=3D545935.8010605@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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