From: Tom Tromey <tom@tromey.com>
To: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
Luis Machado <luis.machado@arm.com>,
alex.bennee@linaro.org, richard.henderson@linaro.org,
peter.maydell@linaro.org
Subject: Re: [PATCH] [gdb/aarch64] pauth: Create new feature string for pauth to prevent crashing older gdb's
Date: Thu, 13 Apr 2023 07:55:46 -0600 [thread overview]
Message-ID: <87r0sn6g4d.fsf@tromey.com> (raw)
In-Reply-To: <9ae7c1bd-64d3-7444-fbc7-e536f8b2f971@arm.com> (Luis Machado via Gdb-patches's message of "Wed, 12 Apr 2023 10:25:56 +0100")
>>>>> "Luis" == Luis Machado via Gdb-patches <gdb-patches@sourceware.org> writes:
Luis> Though it is documentation for users, it is also one of the only
Luis> documents providing guidance for developers of debugging stubs
Luis> (like QEMU's, openOCD etc).
Luis> So I feel like it should include a bit more information rather
Luis> than the bare minimum.
FWIW, I concur -- in the past I've wished that the documentation about
target XML features had been more complete.
Tom
next prev parent reply other threads:[~2023-04-13 13:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 22:43 Luis Machado
2023-04-12 6:05 ` Eli Zaretskii
2023-04-12 8:46 ` Luis Machado
2023-04-12 9:20 ` Eli Zaretskii
2023-04-12 9:25 ` Luis Machado
2023-04-12 9:54 ` Eli Zaretskii
2023-04-12 11:48 ` Peter Maydell
2023-04-12 11:57 ` Luis Machado
2023-04-13 13:55 ` Tom Tromey [this message]
2023-04-12 12:27 ` [PATCH,v2] " Luis Machado
2023-04-12 12:45 ` Eli Zaretskii
2023-04-13 13:56 ` [PATCH, v2] " Tom Tromey
2023-04-13 14:05 ` Luis Machado
2023-04-13 14:37 ` [PATCH, v3] " Luis Machado
2023-04-13 17:17 ` Tom Tromey
2023-04-14 12:45 ` Luis Machado
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=87r0sn6g4d.fsf@tromey.com \
--to=tom@tromey.com \
--cc=alex.bennee@linaro.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=peter.maydell@linaro.org \
--cc=richard.henderson@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).