29 May
2010
29 May
'10
5:29 a.m.
On 05/29/2010 02:06 AM, Jorge Moraleda wrote:
When testing boost.log for race conditions using valgrind drd, some non initialized condition variables are reported at initialization time. I am using Valgrind-3.6.0.SVN and gcc version 4.4.4 (Debian 4.4.4-1).
These are the valgrind error messages:
It looks like a false alarm. The condition variable is defined and used by boost::once, and it is initialized statically in the Boost.Thread library.