From ad1966379db092124dfdaf9585ad496eab676c68 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Thu, 23 Dec 2010 20:29:17 +0000 Subject: [PATCH] gdb/doc/ * gdb.texinfo (Packets) : Document support for registers that were not collected. --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 15 +++++++++++++++ 2 files changed, 20 insertions(+) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index df46a17..31e35d3 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2010-12-23 Pedro Alves + + * gdb.texinfo (Packets) : Document support + for registers that were not collected. + 2010-12-15 Doug Evans * gdb.texinfo (Startup): Document auto-loading of scripts during diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 0e1d553..b48dc70 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -31815,6 +31815,21 @@ each register and their position within the @samp{g} packet are 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 -- 2.7.4