[Valgrind-developers] POSIX.4 semaphores in shared memory

[Bob F. <bfr...@si...>]

Our software is using POSIX.4 semaphores in shared memory.  These 
semaphores are initialized by a different application than the one 
being tested by valgrind.  Valgrind complains vigorously because the 
semaphores are not initialized.

Is there a way around this problem?  Will it help at all if the 
application which initializes the semaphore is also executed under 
valgrind?

It seems like valgrind needs a separate agent program used to collect 
information regarding updates to shared resources so that it can know 
about things like semaphores in shared memory.

Bob
======================================
Bob Friesenhahn
bfr...@si...
http://www.simplesystems.org/users/bfriesen