With apologies to all concerned, and thanks to Aleksey Sanin for tracking down the problem, there is a const-correctness bug in Boost.Regex-1.33.x that strikes only in multithreaded programs on Unix platforms, if: * Multiple threads construct regexes concurrently, or * Multiple threads perform search and replace operations concurrently. There are two possible fixes: * Apply the attached patch (this has just gone into cvs along with an updated test case that detects the issue). Or, * define BOOST_REGEX_USE_C_LOCALE in boost/user.hpp and rebuild everything. Regards, John Maddock.
John Maddock wrote:
There are two possible fixes:
* Apply the attached patch (this has just gone into cvs along with an updated test case that detects the issue). Or, * define BOOST_REGEX_USE_C_LOCALE in boost/user.hpp and rebuild everything.
Can you *please* give some recommendations how to change the bjam build in a way that the patch libraries have a new name, e.g. with an user-defines build id attached (See the postings "bjam issues" or "Labeling patched Boost versions")? Thank you very much, Daniel
Daniel Krügler wrote:
* Apply the attached patch (this has just gone into cvs along with an updated test case that detects the issue). Or, * define BOOST_REGEX_USE_C_LOCALE in boost/user.hpp and rebuild everything.
Can you *please* give some recommendations how to change the bjam build in a way that the patch libraries have a new name, e.g. with an user-defines build id attached (See the postings "bjam issues" or "Labeling patched Boost versions")?
Ah, I um don't actually know how to do that, not without manually hacking the Jamfile so everything has a different base-name :-( John.
participants (2)
-
Daniel Krügler -
John Maddock