id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
1268,xtime_cmp changes to deal with overflow were reverted,oseiler@…,Anthony Williams,"I'm running into this situation when specifying a very long timeout that winds up using boost::condition::timed_wait with an xtime value set up like so:

boost::xtime xt;
boost::xtime_get( &xt, boost::TIME_UTC );
xt.sec += std::numeric_limits<uint32_t>::max(); // ignore potential overflow, as sec is 64-bit
condition.timed_wait( lock, xt ); // <- this returns immediately

Traced this down to an overflow in xtime_cmp (boost/thread/xtime.hpp) that was fixed in version 1.14 of the file and reverted in version 1.15 of the file (replaced with the pre-1.14 version).

This is present in 1.33.1 (version being used on project) and in 1.34.1.",Bugs,closed,To Be Determined,thread,Boost 1.34.1,Problem,wontfix,,