Doesnt "currently asm" indicate asm spinlocks.. Which can be unreliable. These can be even more unreliable with unpatched bdb?
So perhaps you should try posix style semaphores.. Forcing posix/pthreads both at compile time and at run time.. -----Original Message----- From: Howard Chu <h...@symas.com> Sent: Tuesday, 17 February 2009 1:26 AM To: Dieter Kluenter <die...@dkluenter.de> Cc: openldap-devel@openldap.org Subject: Re: 2.4.14 prerelease call for testing #2 Dieter Kluenter wrote: > Aaron Richton<rich...@nbcs.rutgers.edu> writes: [..snip..] > #0 0x00002b77bc3da12d in __lock_detect () > from /usr/local/BerkeleyDB.4.7/lib/libdb-4.7.so > Current language: auto; currently asm Which is pretty squarely inside BerkeleyDB. But nobody else reported any such problem yet. Seems you'll have to check your BDB build.
