public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31202] [gdb/testsuite, aarch64] "[PAC]" in backtrace
Date: Thu, 04 Jan 2024 12:42:28 +0000	[thread overview]
Message-ID: <bug-31202-4717-nZmHnM9vT2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31202-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31202

--- Comment #3 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2bcfdb758bb18e29cf6c0486c448bf78dbbc0c8a

commit 2bcfdb758bb18e29cf6c0486c448bf78dbbc0c8a
Author: Tom de Vries <tdevries@suse.de>
Date:   Thu Jan 4 13:42:45 2024 +0100

    [gdb/testsuite] Handle PAC marker

    On aarch64-linux, I run into:
    ...
    FAIL: gdb.base/annota1.exp: backtrace from shlibrary (timeout)
    ...
    due to the PAC marker showing up:
    ...
    ^Z^Zframe-address^M
    0x000000000041025c [PAC]^M
    ^Z^Zframe-address-end^M
    ...

    In the docs the marker is documented as follows:
    ...
    When GDB is debugging the AArch64 architecture, and the program is using
the
    v8.3-A feature Pointer Authentication (PAC), then whenever the link
register
    $lr is pointing to an PAC function its value will be masked.  When GDB
prints
    a backtrace, any addresses that required unmasking will be postfixed with
the
    marker [PAC].  When using the MI, this is printed as part of the addr_flags
    field.
    ...

    Update the test-case to allow the PAC marker.

    Likewise in a few other test-cases.

    While we're at it, rewrite the affected pattern pat_begin in annota1.exp
into
    a more readable form.  Likewise for the corresponding pat_end.

    Tested on aarch64-linux.

    Approved-By: Luis Machado <luis.machado@arm.com>

    PR testsuite/31202
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31202

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-01-04 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 11:00 [Bug testsuite/31202] New: " vries at gcc dot gnu.org
2024-01-04 11:30 ` [Bug testsuite/31202] " vries at gcc dot gnu.org
2024-01-04 11:30 ` vries at gcc dot gnu.org
2024-01-04 11:32 ` vries at gcc dot gnu.org
2024-01-04 12:42 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-04 12:43 ` vries at gcc dot gnu.org
2024-01-04 16:32 ` kevinb at redhat dot com
2024-01-04 16:50 ` vries at gcc dot gnu.org
2024-01-05 10:00 ` sam at gentoo dot org

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=bug-31202-4717-nZmHnM9vT2@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).