Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc] Remote protocol: undocumented return value for 'p' and 'g'
Date: Fri, 24 Dec 2010 02:50:00 -0000	[thread overview]
Message-ID: <201012232030.15971.pedro@codesourcery.com> (raw)
In-Reply-To: <83sjxoe0ac.fsf@gnu.org>

On Thursday 23 December 2010 19:50:35, Eli Zaretskii wrote:
> > From: Pedro Alves <pedro@codesourcery.com>
> > Okay to apply?
> 
> Yes, thanks.
> 
> > +literal @samp{x}'s in place of the register data digits, to indicate
> > +the corresponding register has not been collected, thus its value is
> 
> "... to indicate that the corresponding register ..."
> 
> > +registers 0 and 2 have not been collected, while registers 1 and 3
> > +have been collected, and have value zero each:
>                         ^^^^^^^^^^^^^^^^^^^^^^^^
> "and both have zero value"
> 

Thanks!  Applied, as below.

-- 
Pedro Alves

2010-12-23  Pedro Alves  <pedro@codesourcery.com>

	gdb/doc/
	* gdb.texinfo (Packets) <read registers packet>: Document support
	for registers that were not collected.

---
 gdb/doc/gdb.texinfo |   15 +++++++++++++++
 1 file changed, 15 insertions(+)

Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo	2010-12-23 20:22:59.000000000 +0000
+++ src/gdb/doc/gdb.texinfo	2010-12-23 20:26:07.000000000 +0000
@@ -31815,6 +31815,21 @@ each register and their position within 
 determined by the @value{GDBN} internal gdbarch functions
 @code{DEPRECATED_REGISTER_RAW_SIZE} and @code{gdbarch_register_name}.  The
 specification of several standard @samp{g} packets is specified below.
+
+When reading registers from a trace frame (@pxref{Analyze Collected
+Data,,Using the Collected Data}), the stub may also return a string of
+literal @samp{x}'s in place of the register data digits, to indicate
+that the corresponding register has not been collected, thus its value
+is unavailable.  For example, for an architecture with 4 registers of
+4 bytes each, the following reply indicates to @value{GDBN} that
+registers 0 and 2 have not been collected, while registers 1 and 3
+have been collected, and both have zero value:
+
+@smallexample
+-> @code{g}
+<- @code{xxxxxxxx00000000xxxxxxxx00000000}
+@end smallexample
+
 @item E @var{NN}
 for an error.
 @end table


      reply	other threads:[~2010-12-23 20:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23 19:52 Pedro Alves
2010-12-23 20:30 ` Eli Zaretskii
2010-12-24  2:50   ` Pedro Alves [this message]

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=201012232030.15971.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=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