Re: [Mingw-w64-public] static debug stl crash on exit with global variable __gnu_cxx::__concurrence_lock_error

2015-07-29 Thread Robin Whittle
I just joined this list and am writing as a reply to a message from Norbert Pfeiler on 2015-05-25. He identified an minimal test program to generate an error, at the end of the executable's run: __gnu_cxx::__concurrence_lock_error when the libstdc++ Debug Mode (bounds checking and the like) is

Re: [Mingw-w64-public] static debug stl crash on exit with global variable __gnu_cxx::__concurrence_lock_error

2015-07-29 Thread Norbert Pfeiler
Hi, this is not specific to 64 bit (in contrast to your conclusion in the TDM bug) and as far as i can tell only happens with a statically linked runtime (which is an inherent property of TDM builds?) In our case we were just curious why our program crashed and i mainly posted it here because i

Re: [Mingw-w64-public] static debug stl crash on exit with global variable __gnu_cxx::__concurrence_lock_error

2015-07-29 Thread Robin Whittle
Hi Norbert, Thanks very much for mentioning static linking. I don't understand how the linker is working. My minimal test program from https://sourceforge.net/p/tdm-gcc/bugs/264/ compiles fine without me giving (via Codelite Project options) any instructions to the linker on where to find

[Mingw-w64-public] static debug stl crash on exit with global variable

2015-05-08 Thread Norbert Pfeiler
Hi all, i have a nice issue for you, took us hours to track down. Compile and run the following with a mingw build with Thread model: posix. #include vector std::vectorint global; int main() { std::vectorint vec; } g++ -static -D_GLIBCXX_DEBUG main.cpp a.exe results in a