Re: [Boost-bugs] [Boost C++ Libraries] #5840: thread.cpp: race condition in thread_proxy's thread state

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #5840: thread.cpp: race condition in thread_proxy's thread state
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2011-12-02 23:00:37

#5840: thread.cpp: race condition in thread_proxy's thread state
---------------------------------+------------------------------------------
  Reporter:  noloader@…          |       Owner:  viboes  
      Type:  Bugs                |      Status:  assigned
 Milestone:  To Be Determined    |   Component:  thread  
   Version:  Boost 1.47.0        |    Severity:  Problem 
Resolution:                      |    Keywords:          
---------------------------------+------------------------------------------
Changes (by viboes):

 * cc: viboes (added)
  * owner:  anthonyw => viboes
  * status:  new => assigned

Comment:

 notify_one doesn't throws. So the single function that could be throw
 after setting m_started is the unlock implied by the scoped_lock. You
 should admit that there are not too many situations on which can lock a
 mutex and immediately after we can not unlock it, isn't it. This will be
 catastrophic, our system will stay with a mutex locked :(

 So in reality I don't think we can fall in the situation you described, or
 maybe I am missing something important.

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