This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/50862] deadlock in std::condition_variable_any
- From: "bartosz.szurgot at pwr dot wroc.pl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 26 Oct 2011 06:39:15 +0000
- Subject: [Bug libstdc++/50862] deadlock in std::condition_variable_any
- Auto-submitted: auto-generated
- References: <bug-50862-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50862
--- Comment #9 from bartek 'basz' szurgot <bartosz.szurgot at pwr dot wroc.pl> 2011-10-26 06:39:15 UTC ---
implementation is nice. i think there is still one more problem to be fixed,
though. namely the line:
~_Unlock() { _M_lock.lock(); }
since lock() may throw an exception, which should never take place in d-tor.
more over, ~_Unlock() can happen to be called because of an exception thrown
from:
_M_cond.wait(__my_lock2);
which means terminate().