Boost logo

Threads-Devel :

Subject: Re: [Threads-devel] locking of boost::timed_mutex results in segmentation fault on linux x64
From: Andriy Tylychko (andriy.tylychko_at_[hidden])
Date: 2010-05-12 03:51:48


> > Linux version 2.6.24-27-generic (buildd_at_crested) (gcc version 4.2.4
> > (Ubuntu 4.2.4-1ubuntu3)) x64
> >
> > intensive usage of boost::timed_mutex::scoped_lock from many threads
> > with the same timed_mutex results in segmentation fault. Sample code
> is
> > attached. It catches SIGSEGV signal in about 5-10 secs of normal
> > operation and prints stack traces.
>
> > What's the problem and how to resolve it?
>
> This is most bizarre. It looks like a problem in
> pthread_mutex_timedlock. It doesn't happen on my linux x64 system, so
> it
> seems really strange that it happens on yours.
>
[AT] It's a known issue of glibc 2.7 that can be reproduced only on
multicore configuration, upgrading glibc should fix the issue


Threads-Devel list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk