diff options
author | Luis Machado <luis.machado@arm.com> | 2023-04-03 10:43:34 +0100 |
---|---|---|
committer | Luis Machado <luis.machado@arm.com> | 2023-04-14 13:44:11 +0100 |
commit | acdf60711d44d20608873bec0376688c9a80e281 (patch) | |
tree | f04f326c4e234c02c15d14d9cf489b00acb9a6ec /gdb/doc | |
parent | e10d82fc3ed03ee03f7c831a5b1e73c6c5ed3722 (diff) | |
download | binutils-gdb-acdf60711d44d20608873bec0376688c9a80e281.tar.gz |
pauth: Create new feature string for pauth to prevent crashing older gdb's
Older gdb's (9, 10, 11 and 12) have a bug that causes them to crash whenever
a target reports the pauth feature string in the target description and also
provide additional register outside of gdb's known and expected feature
strings.
This was fixed in gdb 13 onwards, but that means we're stuck with gdb's out
there that will crash on connection to the above targets.
QEMU has postponed inclusion of the pauth feature string in version 8, and
instead we agreed to use a new feature name to prevent crashing those older
gdb's.
Initially there was a plan to backport a trivial fix all the way to gdb 9, but
given QEMU's choice, this is no longer needed.
This new feature string is org.gnu.gdb.aarch64.pauth_v2, and should be used
by all targets going forward, except native linux gdb and gdbserver, for
backwards compatibility with older gdb's/gdbserver's.
gdb/gdbserver will still emit the old feature string for Linux since it doesn't
report additional system registers and thus doesn't cause a crash of older
gdb's. We can revisit this in the future once the problematic gdb's are likely
no longer in use.
I've added some documentation to explain the situation.
Diffstat (limited to 'gdb/doc')
-rw-r--r-- | gdb/doc/gdb.texinfo | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index c11457952d2..940315b2713 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -47991,6 +47991,29 @@ has a signed link register value that needs to be unmasked/decoded. Extra registers are allowed in this feature, but they will not affect @value{GDBN}. +Please note the @samp{org.gnu.gdb.aarch64.pauth} feature string is deprecated +and must only be used for backwards compatibility with older releases of +@value{GDBN} and @command{gdbserver}. Targets that support Pointer +Authentication must advertise such capability by using the +@samp{org.gnu.gdb.aarch64.pauth_v2} feature string instead. + +The @samp{org.gnu.gdb.aarch64.pauth_v2} feature has the exact same contents +as feature @samp{org.gnu.gdb.aarch64.pauth}. + +The reason for having feature @samp{org.gnu.gdb.aarch64.pauth_v2} is a bug in +previous versions of @value{GDBN} (versions 9, 10, 11 and 12). This bug +caused @value{GDBN} to crash whenever the target reported support for Pointer +Authentication (using feature string @samp{org.gnu.gdb.aarch64.pauth}) and also +reported additional system registers that were not accounted for by +@value{GDBN}. This is more common when using emulators and on bare-metal +debugging scenarios. + +It can also happen if a newer gdbserver is used with an old @value{GDBN} that +has the bug. In such a case, the newer gdbserver might report Pointer +Authentication support via the @samp{org.gnu.gdb.aarch64.pauth} feature string +and also report additional registers the older @value{GDBN} does not know +about, potentially leading to a crash. + @subsubsection AArch64 TLS registers feature The @samp{org.gnu.gdb.aarch64.tls} optional feature was introduced to expose |