On Sat, May 29, 2010 at 7:00 PM, Jorge Moraleda <[email protected]> wrote: > > I submitted a condition variable not initialized detected with > valgrind drd to the boost mailing list, but they report that it is a > false alarm: > > Date: Sat, 29 May 2010 09:29:23 +0400 > From: Andrey Semashev <[email protected]> > > 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). > > 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. > > > These are the valgrind error messages: > > ==27651== condition variable has not been initialized: cond 0x6174420 > ==27651== at 0x4C267B9: pthread_cond_broadc...@* > (drd_pthread_intercepts.c:756) > ==27651== by 0x66DBCD2: ??? (in /usr/local/lib/libboost_log.so.1.42.0) > ==27651== by 0x6719E85: ??? (in /usr/local/lib/libboost_log.so.1.42.0) > ==27651== by 0x66C4BD2: ??? (in /usr/local/lib/libboost_log.so.1.42.0) > ==27651== by 0x7FF000561: ??? > ==27651== by 0x722F63762F656771: ??? > ==27651== by 0x2F6E69622F657068: ??? > ==27651== by 0x722F726576726572: ??? > ==27651== by 0x767265732D657068: ??? > ==27651== by 0x2D2D00772D007264: ??? > ==27651== by 0x72635F776F6C6C60: ??? > ==27651== by 0x62645F65746164: ??? > ==27651== > [ ... ]
Until version 3.5.0 DRD was complaining about every condition variable not initialized by calling pthread_cond_init(). Statically initialized condition variables should be handled properly by trunk r11139. Are you familiar with building Valgrind from the trunk ? If so, can you please test this fix ? Thanks, Bart. ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
