Re: [Boost-users] [thread] assertion error in timed_lock
Dear Anthony,
pthread_mutex_timedlock returned ETIMEDOUT.
This bug has already been fixed.
Of cource, bugs happen. I used boost 1.36.0. Is the fix in 1.37.0? I had installed opensuse 11.1 which was released in december 2008. Boost 1.36.0 was released already in april 2008. Was the error detected so late or are there bug fixes somewhere which could be downloaded? I think there is no 1.36.1? Greetings Ernst
Anthony -- Anthony Williams | Just Software Solutions Ltd Custom Software Development | http://www.justsoftwaresolutions.co.uk Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Dr.-Ing. Ernst Murnleitner T +49 8761 722 00 67 F +49 8761 722 00 59 Awite Bioenergie GmbH Firmensitz: Angerstr. 9 a, D-85416 Langenbach Registergericht München, HRB 162652 Geschäftsführer: Dr.-Ing. Martin Grepmeier, Dr. Ing. Ernst Murnleitner *** Als Anti-Spam-Massnahme können uns EMails von Mail-Servern ohne gültigen ptr-record (Reverse DNS) nicht erreichen ***
On 14/01/2009, Ernst Murnleitner <mur@awite.de> wrote:
Dear Anthony,
pthread_mutex_timedlock returned ETIMEDOUT.
This bug has already been fixed.
Of cource, bugs happen.
I used boost 1.36.0. Is the fix in 1.37.0?
Alas, no. I didn't merge it in time. Boost 1.38 will be out in a few weeks, which WILL have the fix in. For now, just patch your copy to use ETIMEDOUT instead of EBUSY. Anthony -- Anthony Williams Author of C++ Concurrency in Action | http://www.manning.com/williams Custom Software Development | http://www.justsoftwaresolutions.co.uk Just Software Solutions Ltd, Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK
Anthony Williams wrote:
On 14/01/2009, Ernst Murnleitner <mur@awite.de> wrote:
Dear Anthony,
pthread_mutex_timedlock returned ETIMEDOUT.
This bug has already been fixed.
Of cource, bugs happen.
I used boost 1.36.0. Is the fix in 1.37.0?
Alas, no. I didn't merge it in time. Boost 1.38 will be out in a few weeks, which WILL have the fix in. For now, just patch your copy to use ETIMEDOUT instead of EBUSY.
Are you sure? My copy of Boost 1.37.0, file boost/thread/pthread/recursive_mutex.hpp, line 180 looks like this: BOOST_ASSERT(!res || res==ETIMEDOUT); If the previous call to pthread_mutex_timedlock() returns ETIMEDOUT, the assertion should hold. Regards, Peter.
Peter Klotz <peter.klotz@aon.at> writes:
Anthony Williams wrote:
On 14/01/2009, Ernst Murnleitner <mur@awite.de> wrote:
Dear Anthony,
pthread_mutex_timedlock returned ETIMEDOUT.
This bug has already been fixed.
Of cource, bugs happen.
I used boost 1.36.0. Is the fix in 1.37.0?
Alas, no. I didn't merge it in time. Boost 1.38 will be out in a few weeks, which WILL have the fix in. For now, just patch your copy to use ETIMEDOUT instead of EBUSY.
Are you sure?
My copy of Boost 1.37.0, file boost/thread/pthread/recursive_mutex.hpp, line 180 looks like this:
BOOST_ASSERT(!res || res==ETIMEDOUT);
If the previous call to pthread_mutex_timedlock() returns ETIMEDOUT, the assertion should hold.
No, I'm not sure --- I couldn't remember the timings, so I checked my copy of 1.37 (I thought). Checking again, it was indeed fixed in that release. I must have checked 1.36 by mistake. Thanks Peter for correcting me. Anthony -- Anthony Williams | Just Software Solutions Ltd Custom Software Development | http://www.justsoftwaresolutions.co.uk Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL
participants (3)
-
Anthony Williams -
Ernst Murnleitner -
Peter Klotz