https://bugs.kde.org/show_bug.cgi?id=379630
--- Comment #3 from Gregory Nilsson <[email protected]> --- 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.cc -o test -O0 -lstdc++ -lpthread I can see from the output of the -v flag to valgrind REDIR printouts only for pthread_mutex_lock and pthread_mutex_unlock (not pthread_mutex_init/destroy). If I remove -lpthread when compiling then helgrind reports no faults but also no REDIRs can be seen for pthread_mutex, not sure if that is a hint to why you saw no error? I've tried to set SHOW_EVENTS to 1 in hg_main.cc and still cannot see any calls to evh__HG_PTHREAD_MUTEX_DESTROY_PRE. This function would call map_locks_delete() which removes the mutex from the internal lock map of helgrind, but since it is not called then the old mutex will be found when a new mutex is allocated in the same place. Does helgrind detect std::mutex going out of scope on your system? -- You are receiving this mail because: You are watching all bug changes.
