From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Update the 'g' packet documentation
Date: Wed, 11 Jan 2023 21:56:35 +0200 [thread overview]
Message-ID: <831qo0n8uk.fsf@gnu.org> (raw)
In-Reply-To: <20230111183725.2902496-1-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Wed, 11 Jan 2023 11:37:25 -0700)
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Wed, 11 Jan 2023 11:37:25 -0700
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
>
> 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.
> ---
> gdb/doc/gdb.texinfo | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
OK, thanks.
next prev parent reply other threads:[~2023-01-11 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 18:37 Tom Tromey
2023-01-11 19:56 ` Eli Zaretskii [this message]
2023-01-13 12:09 ` Pedro Alves
2023-01-13 18:58 ` Tom Tromey
2023-01-27 15:25 ` [PATCH v2] " Pedro Alves
2023-01-27 16:15 ` Eli Zaretskii
2023-01-30 21:15 ` Tom Tromey
2023-02-16 17:10 ` Pedro Alves
2023-02-16 18:16 ` Tom Tromey
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=831qo0n8uk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).