Boost logo

Boost :

Subject: Re: [boost] Bug reports - Showstoppers and Regressions
From: Vicente Botet (vicente.botet_at_[hidden])
Date: 2012-01-17 08:07:20

Marshall Clow-2 wrote
> There are a couple of useful reports on
> Active Showstoppers:
> Active Regressions:
> IMHO, these bugs should be at least looked at before each release.


Concerning the Boost.Thread showstoppers,

#4521 Error using boost::move on packaged_task (MSVC 10)
#4885 Access violation in set_tss_data at process exit due to invalid
assumption about TlsAlloc
#6174 packaged_task doesn't correctly handle moving results
#6194 Adapt to Boost.Move
#6222 Compile error with SunStudio: unique_future move

Yesterday I made a commit in trunk that should take care of all of them (I
don't think #6222 will behave as expected after the Boost.Move adaptation,
as SunStudio doesn't support well Boost.Move) except #4885.

This commit contains much more that the fix for these Showstoppers. My idea
was to merge the whole to release for 1.50. Should I merge the trunk once
the tester results are good enough or should I merge only the code related
to these Showstoppers?

I don't think that I could have time to take care of #4885 or #6222.


View this message in context:
Sent from the Boost - Dev mailing list archive at

Boost list run by bdawes at, gregod at, cpdaniel at, john at