[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #10 from Paul Floyd --- I still get the same error with CGG 11.2. Your wrapper looks right to me, as long as the pthread_mutex_t is the very first thing in the maemory layout of the std::mutex. That's the case for GCC libstdc++ and I suspec

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #9 from Paul Floyd --- There are two ways to initialize a pthread_mutex_t object: call pthread_mutex_init() or use the static initializer PTHREAD_MUTEX_INITIALIZER The function way is "nice" from a Valgrind perspective since we can intercep

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this mail

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #8 from Gregory Nilsson --- I've created a wrapper for the std::mutex (updated test code attached), with VALGRIND_HG_MUTEX_INIT_POST/VALGRIND_HG_MUTEX_DESTROY_PRE in its constructor/destructor. The lock order violation error is now gone (log

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #7 from Gregory Nilsson --- Created attachment 105411 --> https://bugs.kde.org/attachment.cgi?id=105411&action=edit log when using wrapper -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #6 from Gregory Nilsson --- Created attachment 105409 --> https://bugs.kde.org/attachment.cgi?id=105409&action=edit test case with mutex wrapper -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |C

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #4 from Gregory Nilsson --- Created attachment 105390 --> https://bugs.kde.org/attachment.cgi?id=105390&action=edit drd -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #3 from Gregory Nilsson --- I'm running gcc 4.9.2 and valgrind 3.13 SVN, tried 3.12 as well with the same result. No faults are reported when running DRD (attaching log). I compile my test like this (seen in log.txt): gcc -g -std=c++11 main

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #2 from Ivo Raisr ---

[valgrind] [Bug 379630] false positive std::mutex problems

https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #1 from Gregory Nilsson --- Created attachment 105388 --> https://bugs.kde.org/attachment.cgi?id=105388&action=edit log -- You are receiving this mail because: You are watching all bug changes.