> I'm using helgrind from 3.5.0 on OPENMP code. > > I have a lazily malloc'd pthread mutex in a static global > variable that helgrind detects. > > I'd like to disable the warning somehow in code, not > with a suppression, so that I can look at more interesting > errors.
You can't use Helgrind properly on gcc/g++ compiled OpenMP code as-is, because it doesn't understand the custom synchronisation primitives used by libgomp.so, the support library. One solution which is known to work fairly well is to build gcc with --disable-linux-futex for the top level configure script. This causes libgomp to use pthreads primitives only, which it can see and "understand". Worth a try. J ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
