I forgot to mention that this has been fixed in the 1.33 release. Mike Michael Glassford wrote:
That assertion (and all of the similar loop_count assertions) should be safe to ignore. They were intended as a debugging tool on my part, and weren't supposed to be in the released code.
Mike
Slawomir Lisznianski wrote:
Hello,
I'm using Boost.Threads read/write mutex with the writer scheduling priority. Under heavy load, from many threads, I'm getting the following assertion:
<..>/boost/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:190: void boost::deta il::thread::read_write_mutex_impl<Mutex>::do_write_lock() [with Mutex = boost::mutex]: Assertion `++loop_count == 1' failed. Abort (core dumped)
The system is Linux kernel 2.4.21 (SMP) with 4 CPUs (Intel XEON MP) and g++ 3.2.3 20030502 (Red Hat Linux 3.2.3-42).
Has anyone else experienced a similar problem?
Thanks, Slawomir