Boost C++ Libraries: Ticket #2854: Boost assertion fails inconsistently

John Maddock — Fri, 13 Mar 2009 16:14:30 GMT

Dinesh,

There have been quite a few patches between 1.35 and 1.38, can you try your code with the latest Boost release?

It's also hard to get a feel for which assertion is failing from your backtrace as it looks like you have inline expansions turned on? However, it looks like the smart pointer is NULL, which would typically only happen if one thread is modifying the regex object while another thread is using it: Boost.Regex is threadsafe in the sense that if one thread creates a regex then other threads can access that regex as long as they *all* treat it as constant.

HTH, if you have some information let me know, John Maddock.

dineshkherajani@… — Sat, 14 Mar 2009 10:22:16 GMT

John, Thanks for a promprt response.

void URL::parseUrl()
{
    static const boost::regex e ("^(([^:/?#]+):)?(//)?([^/?#]*)?([^?#]*)(\\?([^#]*))?(#(.*))?");
    boost::smatch subMatch;
    if(regex_match(m_url, subMatch, e))
    {
       ...
    }

This is where I "usually" get an assertion failure.

Assertion failed: 0 != m_pimpl.get(), file ../../../../3rdpartylibs/boostlibs_1.35boost/regex/v4/basic_regex.hpp, line 493

Thanks for your attention.

Dinesh

status changed; resolution set

John Maddock — Mon, 16 Mar 2009 11:53:43 GMT

status new → closed
resolution → invalid

Hi Dinesh,

there is a race condition in your parseURL function: if two threads enter the function at the same time and the variable e has not yet been initialised then one thread will start initialising the variable, but the other thread may then access it before initialisation is complete.

There are two possible workarounds:

1) Make the regular expression a static data member of the URL class - it will then get initialised at program startup. This is then thread safe provided no threads call URL::parseURL before the start of main(). One other downside is that the regex variable will get initialised whether it is used or not: that's not a problem in this one case, but may be if you have a *lot* of such variables.

2) Use boost::call_once to call an initialisation function function that initialises the regex: this isn't cost free either as call_once has a non-zero overhead.

I'm going to close this issue down for now, but please reopen if you find more problems (or this isn't the solution), or if you need the call_once method explaining in more detail.

Regards, John Maddock.