[Valgrind-users] drd with process-shared mutexes

[Howard C. <hy...@sy...>]

The BerkeleyDB library uses blocks of persistent shared memory to store its 
environment state, which includes arrays of interprocess shared mutexes. 
Running an app that uses BDB under valgrind/drd gives a ton of "The object at 
address 0xXXXXXXX is not a mutex." apparently because drd didn't see the 
mutex_init call. (And it won't see it, because the environment and those 
mutexes were initialized by some process other than the one being tested.) Is 
there a way to tell DRD that these mutexes are actually valid, and stop 
complaining about them?
-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/