From: Luis Machado <luis.machado@arm.com>
To: Tom Tromey <tom@tromey.com>,
Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Cc: alex.bennee@linaro.org, richard.henderson@linaro.org,
peter.maydell@linaro.org, eliz@gnu.org
Subject: Re: [PATCH, v2] [gdb/aarch64] pauth: Create new feature string for pauth to prevent crashing older gdb's
Date: Thu, 13 Apr 2023 15:05:59 +0100 [thread overview]
Message-ID: <e1e51661-81a6-e554-50a0-e6b7091b001a@arm.com> (raw)
In-Reply-To: <87mt3b6g2q.fsf@tromey.com>
On 4/13/23 14:56, Tom Tromey wrote:
>>>>>> "Luis" == Luis Machado via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Luis> +In the future the @samp{org.gnu.gdb.aarch64.pauth} feature string might be
> Luis> +deprecated in favor of feature string @samp{org.gnu.gdb.aarch64.pauth_v2}.
>
> Is there a particular reason to say "might be", rather than just
> deprecate it directly? Like would gdb ever go back to the non _v2
> feature name?
Not really. I was going for flexibility. But in this case, we won't go back to using the
old feature string. We just need to use the old one for backwards compatibility while we
wait for older broken gdb's to vanish.
I'll update it.
next prev parent reply other threads:[~2023-04-13 14:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 22:43 [PATCH] " 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
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 [this message]
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=e1e51661-81a6-e554-50a0-e6b7091b001a@arm.com \
--to=luis.machado@arm.com \
--cc=alex.bennee@linaro.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=peter.maydell@linaro.org \
--cc=richard.henderson@linaro.org \
--cc=tom@tromey.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).