Hi, I suffer from the same bug in one of my projects, which keeps the program from running. I also tested the code posted by David, and as he said the program never reaches "After". I'm using libboost 1.32.0-2 on Debian GNU/Linux. PS: I haven't seen any entry for this in the boost bug tracking system yet. Maybe one ought to be created? Regards, Tanguy Michael Glassford wrote:
Just wanted to let you know: unfortunately, I won't be able to look at this until at least this weekend. If anyone else wants to volunteer, help would be welcome.
Mike
"David Brownell" <david_brownell@hotmail.com> wrote in message news:BAY101-DAV107F654EE1B22D622CD3CEEDBF0@phx.gbl...
When running the simple program listed below, the scoped_read_lock appears to never acquire a read lock on the mutex and, as a result, the program never finishes. In looking through the documentation, I don't think there is anything additional I need to do and was a bit surprised that this didn't work.
Here is the code:
boost::read_write_mutex m(static_cast<boost::read_write_scheduling_policy::read_write_scheduling_pol icy_enum>(alternating_many_reads));
std::cout << "Before\n"; { boost::read_write_mutex::scoped_write_lock l(m); } std::cout << "Middle\n"; { boost::read_write_mutex::scoped_read_lock l(m); } std::cout << "After\n";
And some more details: - Windows XP SP2 - Microsoft Visual Studio 2003 - I am compiling with the Multithreaded DLL version of the CRT, so boost_thread-vc71-mt-gd-1_32.lib is being used - test_read_write_mutex.cpp completed without problems - writer_priority and reader_priority completed without problems. Only alternating_many_reads and alternating_single_read seem to have problems.
Thanks for your help! David Brownell