public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bartosz.szurgot at pwr dot wroc.pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/50862] New: deadlock in std::condition_variable_any Date: Tue, 25 Oct 2011 10:27:00 -0000 [thread overview] Message-ID: <bug-50862-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50862 Bug #: 50862 Summary: deadlock in std::condition_variable_any Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: major Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: bartosz.szurgot@pwr.wroc.pl Created attachment 25610 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25610 proof of concept for deadlock there is a dead lock when using wait() method of std::condition_variable_any (condition_variable:199) from more than one thread. it happens when method locks two mutexes (local and user-provided), when condition is met, in a different order than when entering.
next reply other threads:[~2011-10-25 10:27 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-25 10:27 bartosz.szurgot at pwr dot wroc.pl [this message] 2011-10-25 10:28 ` [Bug libstdc++/50862] " bartosz.szurgot at pwr dot wroc.pl 2011-10-25 11:27 ` redi at gcc dot gnu.org 2011-10-25 13:00 ` redi at gcc dot gnu.org 2011-10-25 13:52 ` bartosz.szurgot at pwr dot wroc.pl 2011-10-25 14:10 ` redi at gcc dot gnu.org 2011-10-25 14:45 ` bartosz.szurgot at pwr dot wroc.pl 2011-10-25 20:57 ` redi at gcc dot gnu.org 2011-10-25 22:29 ` redi at gcc dot gnu.org 2011-10-26 6:39 ` bartosz.szurgot at pwr dot wroc.pl 2011-10-26 10:30 ` redi at gcc dot gnu.org 2011-10-26 12:42 ` bartosz.szurgot at pwr dot wroc.pl 2011-10-26 13:03 ` redi at gcc dot gnu.org 2011-10-26 13:06 ` redi at gcc dot gnu.org 2011-10-26 13:43 ` bartosz.szurgot at pwr dot wroc.pl 2011-10-26 13:55 ` aoliva at gcc dot gnu.org 2011-10-26 14:06 ` redi at gcc dot gnu.org 2011-10-26 23:36 ` redi at gcc dot gnu.org 2011-12-19 0:35 ` redi at gcc dot gnu.org 2011-12-19 0:56 ` 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-50862-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).