From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2005-12-01 15:36:05
> Initial Comment:
> When using BOOST+AUTO_UNIT_TEST and
> BOOST_SP_USE_QUICK_ALLOCATOR and BOOST_HAS_THREADS
> macros under Windows (MSVC71) Access Violation occurs
> in "lightweight_mutex::scoped_lock::scoped_lock".
> This behavior produced by error in
> "boost::detail::allocator_impl" or in Test Framework.
> Mutex for locking created by static member. Automatic
> unittests created by using global variables. So we have
> using uninitialized CRITICAL_SECTION because order of
> global variables initialization is undefined.
> I tried to convert
> "boost::detail::allocator_impl::mutex" from static
> variable to Meyer's singleton (with static member
> function which contains local static variable "mutex").
> This solves my problem but I can't suggest any patch
> because I can't test it with many compilers.
This is frequently met issue with global variables. Peter will you be able
to handle this?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk