[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-13 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 --- Comment #9 from Jonathan Wakely 2012-08-13 14:35:21 UTC --- Perfect - thanks. I'll get it committed tonight.

[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-13 Thread d.adler.s at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 --- Comment #8 from David Adler 2012-08-13 14:09:16 UTC --- Created attachment 28005 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28005 proposed changelog I wasn't sure about the testcase file name, so I just guessed.

[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-12 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 --- Comment #7 from Jonathan Wakely 2012-08-12 16:22:28 UTC --- I need a ChangeLog entry before I can commit the change, which needs your name, could you provide a ChangeLog entry? Thanks. Unless I'm mistaken the volatile qualifiers in the test

[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-06 Thread architectbum at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 --- Comment #6 from architectbum at hotmail dot com 2012-08-06 17:18:26 UTC --- I don't have this_thread::sleep_for in my build, but presumably it wouldn't help as the segfault comes inside the pthread_cond_wait function. The testcase as written al

[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-06 Thread amonakov at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 Alexander Monakov changed: What|Removed |Added CC||amonakov at gcc dot gnu.org --- Comme

[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-06 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 --- Comment #4 from Jonathan Wakely 2012-08-06 14:30:31 UTC --- Thanks very much. For this sort of test it doesn't need to fail every time, the GCC testsuite is run often enough on a wide enough variety of systems that even if the test only fails

[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-06 Thread architectbum at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 --- Comment #3 from architectbum at hotmail dot com 2012-08-06 14:20:03 UTC --- Because the problem is in thread-handling code, it's impossible to create a completely deterministic testcase; however, the newly-attached testcase.cc (compiled with 'g

[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-06 Thread architectbum at hotmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 --- Comment #2 from architectbum at hotmail dot com 2012-08-06 14:19:16 UTC --- Created attachment 27952 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27952 testcase

[Bug libstdc++/54185] condition_variable not properly destructed

2012-08-06 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54185 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|