public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/31202] New: [gdb/testsuite, aarch64] "[PAC]" in backtrace Date: Sun, 31 Dec 2023 11:00:44 +0000 [thread overview] Message-ID: <bug-31202-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31202 Bug ID: 31202 Summary: [gdb/testsuite, aarch64] "[PAC]" in backtrace Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- On aarch64-linux I'm running into a cluster of fails in these test-cases: ... #rtf=gdb.base/annota1.exp #rtf=gdb.cp/exception.exp #rtf=gdb.dwarf2/entry-value-typedef.exp #rtf=gdb.mi/mi-syn-frame.exp #rtf=gdb.mi/mi-catch-cpp-exceptions.exp #rtf=gdb.threads/pthread_cond_wait.exp #rtf=gdb.threads/tls.exp ... For example, in more detail: ... gdb) PASS: gdb.cp/exception.exp: continue to first throw backtrace^M #0 0x0000fffff7ddcf30 in __cxa_throw () from /lib64/libstdc++.so.6^M #1 0x0000000000410260 [PAC] in foo (i=20) at /home/vries/gdb/src/gdb/testsuite/gdb.cp/exception.cc:23^M #2 0x00000000004102b4 in main () at /home/vries/gdb/src/gdb/testsuite/gdb.cp/exception.cc:45^M (gdb) FAIL: gdb.cp/exception.exp: backtrace after first throw ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-12-31 11:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-31 11:00 vries at gcc dot gnu.org [this message] 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 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@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: 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).