Opened 13 years ago

Closed 13 years ago

#4121 closed Bugs (invalid)

locking of boost::timed_mutex results in segmentation fault on linux x64

Reported by: Andrew Tylychko <andriy.tylychko@…> Owned by: Anthony Williams
Milestone: Boost 1.43.0 Component: thread
Version: Boost 1.42.0 Severity: Showstopper
Keywords: Cc:

Description

Linux version 2.6.24-27-generic (buildd@crested) (gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)) #1 SMP Fri Mar 12 00:52:19 UTC 2010 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.

Stack traces show:

#5 <signal handler called>

#6 0x00007f5834551244 in lll_timedlock_wait () from /lib/libpthread.so.0

#7 0x00007f583454d9ac in _L_timedlock_161 () from /lib/libpthread.so.0

#8 0x00007f583454d230 in pthread_mutex_timedlock () from /lib/libpthread.so.0

#9 0x000000000040a2f0 in thread_func ()

Attachments (1)

mutex_test.zip​ (1.6 KB ) - added by Andrew Tylychko <andriy.tylychko@…> 13 years ago.
sample code

Download all attachments as: .zip

Change History (2)

by Andrew Tylychko <andriy.tylychko@…>, 13 years ago

Attachment: mutex_test.zip​ added

sample code

comment:1 by Andrew Tylychko <andriy.tylychko@…>, 13 years ago

Resolution: → invalid
Status: new → closed

seems it's the kernel problem described here: ​https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/284672

Note: See TracTickets for help on using tickets.