public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105730] [12/13 Regression] Issue with commit - Allow std::condition_variable waits to be cancelled Date: Wed, 21 Dec 2022 12:10:27 +0000 [thread overview] Message-ID: <bug-105730-4-zg1lhFCnFe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105730-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105730 --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- It seems like a problem with symbol resolution either during linking, or when loading the dynamic library. The old _ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE@GLIBCXX_3.4.11 symbol is an alias for __gnu_cxx::__nothrow_wait_cv::wait which calls the new std::condition_variable::wait(unique_lock<mutex>&)@@GLIBCXX_3.4.30 symbol. But here it's calling itself recursively, leading to a stack overflow segfault. The call from __gnu_cxx::__nothrow_wait_cv::wait *should* bind to the new symbol with version @@GLIBCXX_3.4.30 instead of the old one which is an alias to itself.
next prev parent reply other threads:[~2022-12-21 12:10 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-25 17:32 [Bug libstdc++/105730] New: " lancethepants at gmail dot com 2022-05-26 9:18 ` [Bug libstdc++/105730] " marxin at gcc dot gnu.org 2022-05-26 9:18 ` marxin at gcc dot gnu.org 2022-10-25 7:17 ` [Bug libstdc++/105730] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-10-25 11:57 ` redi at gcc dot gnu.org 2022-10-25 12:01 ` redi at gcc dot gnu.org 2022-12-20 13:48 ` rguenth at gcc dot gnu.org 2022-12-20 15:50 ` pinskia at gcc dot gnu.org 2022-12-21 11:52 ` redi at gcc dot gnu.org 2022-12-21 12:10 ` redi at gcc dot gnu.org [this message] 2022-12-21 12:24 ` glex.spb at gmail dot com 2022-12-21 13:22 ` redi at gcc dot gnu.org 2022-12-21 13:22 ` redi at gcc dot gnu.org 2022-12-21 13:45 ` glex.spb at gmail dot com 2022-12-22 23:35 ` cvs-commit at gcc dot gnu.org 2023-01-17 18:25 ` [Bug libstdc++/105730] [12 " lancethepants at gmail dot com 2023-01-17 19:01 ` redi at gcc dot gnu.org 2023-01-17 19:23 ` glex.spb at gmail dot com 2023-01-18 15:14 ` cvs-commit at gcc dot gnu.org 2023-01-18 15:15 ` 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-105730-4-zg1lhFCnFe@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).