public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Pedro Alves <palves@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Update the 'g' packet documentation Date: Thu, 16 Feb 2023 17:12:44 +0000 (GMT) [thread overview] Message-ID: <20230216171244.9E4823858D33@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=16b84b6599dba01abc00954d0bc80ddf0c2373e3 commit 16b84b6599dba01abc00954d0bc80ddf0c2373e3 Author: Tom Tromey <tom@tromey.com> Date: Wed Jan 11 11:37:25 2023 -0700 Update the 'g' packet documentation The 'g' packet documentation references a macro that no longer exists, and it also claims that the 'x' response for an unavailable register is limited to trace frames. This patch updates the documentation to reflect what I think is currently correct. Co-Authored-By: Pedro Alves <pedro@palves.net> Approved-By: Eli Zaretskii <eliz@gnu.org> Change-Id: I863baa3b9293059cfd4aa3d534602cbcb693ba87 Diff: --- gdb/doc/gdb.texinfo | 30 ++++++++++++++++++++---------- 1 file changed, 20 insertions(+), 10 deletions(-) diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 8c2cd23df18..3642828eb0e 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -41770,17 +41770,27 @@ Reply: Each byte of register data is described by two hex digits. The bytes with the register are transmitted in target byte order. The size of 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}. - -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 +determined by the target description (@pxref{Target Descriptions}); in +the absence of a target description, this is done using code internal +to @value{GDBN}; typically this is some customary register layout for +the architecture in question. + +When reading registers, 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's value is unavailable. For example, when +reading registers from a trace frame (@pxref{Analyze Collected +Data,,Using the Collected Data}), this means that the register has not +been collected in the trace frame. When reading registers from a live +program, this indicates that the stub has no means to access the +register contents, even though the corresponding register is known to +exist. Note that if a register truly does not exist on the target, +then it is better to not include it in the target description in the +first place. + +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: +registers 0 and 2 are unavailable, while registers 1 and 3 +are available, and both have zero value: @smallexample -> @code{g}
reply other threads:[~2023-02-16 17:12 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=20230216171244.9E4823858D33@sourceware.org \ --to=palves@sourceware.org \ --cc=gdb-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).