Re: [Boost-bugs] [Boost C++ Libraries] #8323: boost::thread::try_join_for/try_join_until may block indefinitely due to a combination of problems in Boost.Thread and Boost.Chrono

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8323: boost::thread::try_join_for/try_join_until may block indefinitely due to a combination of problems in Boost.Thread and Boost.Chrono
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-03-30 09:02:36


#8323: boost::thread::try_join_for/try_join_until may block indefinitely due to a
combination of problems in Boost.Thread and Boost.Chrono
-----------------------------------------+----------------------------------
  Reporter: szakharchenko@… | Owner: viboes
      Type: Bugs | Status: assigned
 Milestone: To Be Determined | Component: thread
   Version: Boost 1.50.0 | Severity: Problem
Resolution: | Keywords: thread, chrono, steady_clock, try_jon_for, try_join_until, QueryPerformanceCounter
-----------------------------------------+----------------------------------

Comment (by viboes):

 Replying to [comment:1 viboes]:
> Hi,
>
> It is strange to me that successive calls to steady_clock::now() are not
 monotonic. The trace you gave got the second call to steady_clock::now()
 5591679763370 which is GT the fist one 5591678518200
>
> {{{
>
> t = rep_ =
 5591678518200
> typename Clock::time_point c_now = Clock::now() = rep_ =
 5591679763370
> ^
> }}}
>
> What am I missing?

 Any news on this?

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

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:12 UTC