public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31293] gdb.threads/threadcrash.exp failure Date: Thu, 25 Jan 2024 12:57:08 +0000 [thread overview] Message-ID: <bug-31293-4717-tVuxDRVPxb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31293-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31293 --- Comment #1 from Guinevere Larsen <blarsen at redhat dot com> --- I don't think this is a problem in the test. The point of the test is that we should be able to unwind correctly all frames. Since the backtrace of the failure does contain "??", the test is flagging a real issue in Debian 12, I think. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-25 12:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-25 12:44 [Bug gdb/31293] New: " simon.marchi at polymtl dot ca 2024-01-25 12:44 ` [Bug gdb/31293] " simon.marchi at polymtl dot ca 2024-01-25 12:57 ` blarsen at redhat dot com [this message] 2024-03-05 7:30 ` [Bug testsuite/31293] " vries at gcc dot gnu.org 2024-03-11 9:57 ` cvs-commit at gcc dot gnu.org 2024-03-11 9:59 ` vries 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-31293-4717-tVuxDRVPxb@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).