Aaron Richton wrote:
I'm on latest 0.9.7 release. I can try and put together a slapd with 0.9.8d, and I guess if we're going to (potentially?) be pointing fingers toward OpenSSL that's a good idea anyway...
Yes, definitely a good idea. The prior releases always used getpid() to determine the threadID of the current thread, to decide if locking was needed. This is obviously only correct on old systems running LinuxThreads, where each thread was actually a separate process. It's surprising that it wasn't until recently that we've started seeing crashes caused by this bug.
On Tue, 28 Nov 2006, Howard Chu wrote:
richton@nbcs.rutgers.edu wrote:
Here's another, although without a malloc debugger:
What would be good ways to go about figuring out if this is an issue with the SSL library or slapd's usage thereof?
What version of OpenSSL are you using? I've definitely encountered locking issues in 0.9.7 and early 0.9.8 releases. Some of those are supposed to be fixed in the latest 0.9.8.
-- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc OpenLDAP Core Team http://www.openldap.org/project/
.