This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/66096] Unexpected __gnu_cxx::__concurrence_lock_error with _GLIBCXX_DEBUG
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 12 May 2015 07:56:57 +0000
- Subject: [Bug c++/66096] Unexpected __gnu_cxx::__concurrence_lock_error with _GLIBCXX_DEBUG
- Auto-submitted: auto-generated
- References: <bug-66096-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66096
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|32 bit |x86_64-w64-mingw32
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2015-05-12
Host|Windows 7 x64 |x86_64-w64-mingw32
Ever confirmed|0 |1
Build|g++.EXE (tdm-1) 4.9.2 |
|Copyright (C) 2014 Free |
|Software Foundation, Inc. |
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This report is not very useful without a stack trace showing where the
exception is thrown. I suspect it's a mingw-w64 problem as it doesn't happen on
other targets, so there may be nothing to fix in the upstream libstdc++ code.
As requested at https://gcc.gnu.org/bugs/ please provide the output of 'gcc -v'
not just the version number.