From: Luis Machado <luis.machado@arm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org, alex.bennee@linaro.org,
richard.henderson@linaro.org
Subject: Re: [PATCH] [gdb/aarch64] pauth: Create new feature string for pauth to prevent crashing older gdb's
Date: Wed, 12 Apr 2023 12:57:31 +0100 [thread overview]
Message-ID: <561837b3-a998-8c28-c2e5-bbb169436679@arm.com> (raw)
In-Reply-To: <CAFEAcA9Q6mA+mYXD2ccHam=R5y_QwtOUFuomHZYoBvgGntdy0w@mail.gmail.com>
On 4/12/23 12:48, Peter Maydell wrote:
> On Wed, 12 Apr 2023 at 10:26, Luis Machado <luis.machado@arm.com> wrote:
>> On 4/12/23 10:20, Eli Zaretskii wrote:
>>> Is it really important to say that the bug happens only when
>>> additional system registers are reported?
>>
>> We could make it shorter by only mentioning this is only an issue when using emulators.
>
> It's not emulator-specific, though, is it, if I understand the bug right?
> It will happen with any gdb-protocol-speaking stub that reports registers
> in XML features that gdb doesn't care about, I think you said? It's just
> that the case we know about happens to be with an emulator where the
> extra registers reported are system registers.
Yes, that's true. That was oversimplifying it. Emulators would be the most common case at the moment, like QEMU users
attempting to use Pointer Authentication support.
It could be potentially anything, as I described before. Even a newer gdbserver talking to an old gdb, if the new gdbserver
sends additional registers the old gdb doesn't care about.
Maybe I should expand on that explanation as well.
>
> thanks
> -- PMM
next prev parent reply other threads:[~2023-04-12 11:57 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 [this message]
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
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=561837b3-a998-8c28-c2e5-bbb169436679@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 \
/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).