Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:doco] Add ``maint print registers''
Date: Sun, 11 Aug 2002 09:40:00 -0000	[thread overview]
Message-ID: <3D56938C.9060908@ges.redhat.com> (raw)
In-Reply-To: <2593-Sun11Aug2002164401+0300-eliz@is.elta.co.il>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

Try this, its better :-)

>> Date: Fri, 09 Aug 2002 20:07:17 -0400
>> From: Andrew Cagney <ac131313@ges.redhat.com>
>> 
>> 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.
> 
> 
> Perhaps an example of raw and cooked representation will help here.

Hmm, it now states exactly what raw/cooked print and gives the 
reference.  (No, the Node isn't in the gdbint file yet :-)

>> ok?
> 
> 
> Yes, thanks.
> 
> 
>> +@item @anchor{maint print registers}maint print registers
> 
> 
> Why did you use @anchor here, if no other parts of the manual have
> any @xref's pointing to them?
> 

Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1085 bytes --]

2002-08-11  Andrew Cagney  <ac131313@redhat.com>

	* gdb.texinfo (Maintenance Commands): Document "maint print
	registers", "maint print raw-registers" and "maint print
	cooked-registers".

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.110
diff -u -r1.110 gdb.texinfo
--- gdb.texinfo	10 Aug 2002 00:40:40 -0000	1.110
+++ gdb.texinfo	11 Aug 2002 16:34:46 -0000
@@ -14195,6 +14195,21 @@
 
 @end table
 
+@kindex maint print registers
+@kindex maint print raw-registers
+@kindex maint print cooked-registers
+@item maint print registers
+@itemx maint print raw-registers
+@itemx maint print cooked-registers
+Print @value{GDBN}'s internal register data structures.
+
+The command @samp{maint print raw-registers} includes the contents of
+the raw register cache; and the command @samp{maint print
+cooked-registers} includes the (cooked) value of all registers.
+@xref{Registers,, Registers, gdbint, @value{GDBN} Internals}.
+
+Takes an optional file parameter.
+
 @end table
 
 

  reply	other threads:[~2002-08-11 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09 17:07 Andrew Cagney
2002-08-11  6:46 ` Eli Zaretskii
2002-08-11  9:40   ` Andrew Cagney [this message]
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=3D56938C.9060908@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=eliz@is.elta.co.il \
    --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