public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libbacktrace/112263] [C++23] std::stacktrace does not identify symbols in shared library Date: Sat, 04 Nov 2023 05:56:16 +0000 [thread overview] Message-ID: <bug-112263-4-xb2rHPumX5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112263-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-11-04 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I think we can mark this as confirmed since there is a patch submitted and the duplicated bug confirmed that patch fixes the issue.
next prev parent reply other threads:[~2023-11-04 5:56 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-28 15:35 [Bug libstdc++/112263] New: " vincenzo.innocente at cern dot ch 2023-10-28 21:04 ` [Bug libstdc++/112263] " redi at gcc dot gnu.org 2023-10-30 13:43 ` [Bug libbacktrace/112263] " vincenzo.innocente at cern dot ch 2023-10-31 1:07 ` ian at airs dot com 2023-10-31 10:45 ` vincenzo.innocente at cern dot ch 2023-11-01 11:16 ` vincenzo.innocente at cern dot ch 2023-11-01 13:09 ` vincenzo.innocente at cern dot ch 2023-11-03 3:05 ` ian at airs dot com 2023-11-03 9:55 ` vincenzo.innocente at cern dot ch 2023-11-03 16:32 ` redi at gcc dot gnu.org 2023-11-04 5:56 ` pinskia at gcc dot gnu.org [this message] 2023-11-05 0:05 ` ian at airs dot com 2023-11-05 10:49 ` vincenzo.innocente at cern dot ch 2023-11-06 23:11 ` cvs-commit at gcc dot gnu.org 2023-11-06 23:12 ` cvs-commit at gcc dot gnu.org 2023-11-06 23:13 ` cvs-commit at gcc dot gnu.org 2023-11-06 23:13 ` ian at airs dot com 2023-11-06 23:30 ` redi 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-112263-4-xb2rHPumX5@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).