Processed: Re: Bug#810868: threads: condition_variable or atomic causes _sometimes_ a deadlock

Processing control commands: > tags -1 + moreinfo Bug #810868 [g++-4.9] threads: condition_variable or atomic causes _sometimes_ a deadlock Added tag(s) moreinfo. -- 810868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810868 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#810868: threads: condition_variable or atomic causes _sometimes_ a deadlock

Control: tags -1 + moreinfo On 13.01.2016 02:44, U.Mutlu wrote: Package: g++-4.9 Version: 4.9.2-10 Severity: normal please recheck with gcc-4.9, gcc-5 from unstable, and gcc-6 from experimental.

Bug#810868: threads: condition_variable or atomic causes _sometimes_ a deadlock

I have been able to locate the bug: The implementation of the non-lambda version of condition_variable.wait() in my compiler (g++ (Debian 4.9.2-10) 4.9.2) seems to be buggy; I guess it is also in the other versions of g++. One can simulate the buggy behaviour by enabling the 2 ifdef's below. The

Bug#810868: threads: condition_variable or atomic causes _sometimes_ a deadlock

Package: g++-4.9 Version: 4.9.2-10 Severity: normal Dear Maintainer, there is a mysterious bug in g++ or its libraries. The bug happens when one compiles and executes the following test code multiple times: sometimes the executable just hangs, ie. a deadlock happens. I think the error lies not in