public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94514] New: aarch64: unwinding across mixed pac-ret and non-pac-ret frames is broken Date: Tue, 07 Apr 2020 11:28:36 +0000 [thread overview] Message-ID: <bug-94514-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94514 Bug ID: 94514 Summary: aarch64: unwinding across mixed pac-ret and non-pac-ret frames is broken Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: nsz at gcc dot gnu.org Target Milestone: --- libgcc unwinder on aarch64 fails to keep track of pauth state and may try to authenticate return addresses that were not signed causing a runtime crash. example c++ code that segfaults in the unwinder on a pauth enabled system: __attribute__((noinline, target("branch-protection=pac-ret"))) static void do_throw (void) { throw 42; __builtin_abort (); } __attribute__((noinline, target("branch-protection=none"))) static void no_pac_ret (void) { do_throw (); __builtin_abort (); } int main () { try { no_pac_ret (); } catch (...) { return 0; } __builtin_abort (); }
next reply other threads:[~2020-04-07 11:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-07 11:28 nsz at gcc dot gnu.org [this message] 2020-04-21 16:50 ` [Bug target/94514] " cvs-commit at gcc dot gnu.org 2020-04-23 13:18 ` cvs-commit at gcc dot gnu.org 2020-05-14 15:17 ` cvs-commit at gcc dot gnu.org 2020-05-14 15:48 ` cvs-commit at gcc dot gnu.org 2020-05-14 15:51 ` nsz at gcc dot gnu.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-94514-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).