Boost C++ Libraries: Ticket #5840: thread.cpp: race condition in thread_proxy's thread state

component changed; owner set

Wed, 31 Aug 2011 00:45:02 GMT

owner set to Anthony Williams
component None → thread

owner, status changed; cc set

viboes — Fri, 02 Dec 2011 23:00:36 GMT

cc viboes added
owner changed from Anthony Williams to viboes
status new → assigned

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.

type changed

viboes — Wed, 07 Dec 2011 00:38:21 GMT

type Bugs → Support Requests

Move so Support request until resolution clarified.

status, type changed; resolution set

viboes — Tue, 20 Dec 2011 17:24:57 GMT

status assigned → closed
type Support Requests → Bugs
resolution → invalid

It seems the described situation can not be occur.

Please, reopen it if you don't agree with the resolution.