This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier
- From: "edwintorok at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Jan 2010 17:54:18 -0000
- Subject: [Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier
- References: <bug-42624-15165@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #13 from edwintorok at gmail dot com 2010-01-12 17:54 -------
(In reply to comment #12)
> Thread 1 waits for its colleagues, but where are they gone? Is it possible
> that an exception is thrown inside find (by means of the value type or the
> predicate)?
> I don't fully trust gdb in this case, but it shows that an iterator range of
> (NULL, NULL) had to be searched.
>
This code is compiled with -fno-exceptions, could that be a problem?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42624