public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "i.hamsa at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98108] New: Broken Schwarz counter for iostreams initialization Date: Wed, 02 Dec 2020 21:32:36 +0000 [thread overview] Message-ID: <bug-98108-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98108 Bug ID: 98108 Summary: Broken Schwarz counter for iostreams initialization Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: i.hamsa at gmail dot com Target Milestone: --- Iostreams initialization doesn't work in multithreaded environments. To reproduce one needs two source files: // file1.cc #include <thread> void threadfunc(); struct StaticThread { std::thread t; StaticThread() : t(threadfunc) {} ~StaticThread() { t.join(); } }; static StaticThread thread1, thread2; //file2.cc #include <iostream> void threadfunc() { std::cout << "Printing\n"; } int main() {} //compile g++ -pthread file1.cc file2.cc It is important that <iostream> is NOT included in file1.cc. The resulting executable always crashes on my machine (Gentoo Linux). Add <iostream> to file1.cc, the crash disappears. Change the order of source files in the command line, the crash disappears. --- The culprit is ios_base::Init::_S_refcount. Basically it is an atomic nifty counter. The problem is, the nifty counter idiom doesn't work with multithreading. Making it atomic achieves absolutely nothing. If we have two or more threads that can enter Init::Init() at the same time, one should proceed and the rest must WAIT. It is the same thing as initialization of a static object in a block scope, and should be interlocked in exactly the same way.
next reply other threads:[~2020-12-02 21:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-02 21:32 i.hamsa at gmail dot com [this message] 2020-12-03 7:28 ` [Bug libstdc++/98108] " rguenth at gcc dot gnu.org 2020-12-03 9:19 ` i.hamsa at gmail dot com 2020-12-09 15:52 ` redi at gcc dot gnu.org 2020-12-15 11:45 ` cvs-commit at gcc dot gnu.org 2020-12-15 11:53 ` redi at gcc dot gnu.org 2020-12-15 18:42 ` cvs-commit at gcc dot gnu.org 2020-12-16 16:16 ` redi at gcc dot gnu.org 2020-12-16 17:41 ` i.hamsa at gmail dot com 2020-12-16 23:32 ` redi at gcc dot gnu.org 2022-11-06 16:16 ` cvs-commit 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-98108-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).