Re: [Boost-bugs] [Boost C++ Libraries] #3585: Boost::thread + valgrind/drd possible false positive

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3585: Boost::thread + valgrind/drd possible false positive
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-12-04 17:00:22

#3585: Boost::thread + valgrind/drd possible false positive
-----------------------------------------------------+----------------------
  Reporter:  Mihail Strashun <m.strashun@…>          |       Owner:  anthonyw             
      Type:  Bugs                                    |      Status:  new                  
 Milestone:  To Be Determined                        |   Component:  thread               
   Version:  Boost 1.42.0                            |    Severity:  Problem              
Resolution:                                          |    Keywords:  thread, drd, valgrind
-----------------------------------------------------+----------------------

Comment (by viboes):

 Replying to [comment:4 bvanassche@…]:
 > As far as I can see thread_data_base::current_cond is signaled by
 thread::interrupt() but is never waited upon. That kind of access pattern
 is safe. This also means that it is safe to remove the member variable
 thread_data_base::current_cond from the Boost thread library.


 Not yet. Have you take a look at libs/thread/src?


 {{{
 grep -rHn current_cond *
 src/pthread/thread.cpp:416:            if(local_thread_info->current_cond)
 src/pthread/thread.cpp:419:
 BOOST_VERIFY(!pthread_cond_broadcast(local_thread_info->current_cond));

 }}}



 {{{
 416             if(local_thread_info->current_cond)
 417             {
 418                 boost::pthread::pthread_mutex_scoped_lock
 internal_lock(local_thread_info->cond_mutex);
 419
 BOOST_VERIFY(!pthread_cond_broadcast(local_thread_info->current_cond));
 420             }
 }}}

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/3585#comment:5>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.