[Date Prev][Date Next]
Precluding hardware-dependent issues
- To: openldap-software@OpenLDAP.org
- Subject: Precluding hardware-dependent issues
- From: Michael Ströder <firstname.lastname@example.org>
- Date: Tue, 17 Feb 2009 13:27:17 +0100
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20081204 SeaMonkey/1.1.14
I have strange seg faults when sending a SASL/DIGEST-MD5 bind with
OpenLDAP 2.4.11 running with BDB 4.6.21p1 on different VMware machines
running with SLES 10. I plan to update both software packages anyway
but, as usual, the customer is a little bit scared of upgrading. ;-)
I'd also like to figure out what the real problem is since on one
machine it simply works and it does not on another.
I've checked pre-installed SuSE packages, all related config files, file
ownership/permissions and dynamic linking of slapd (ldd output).
Everything seems ok. Start over with slapadd-ing to an empty DB didn't
help either. Running slapd -d 32767 on the concole shows that the SASL
user is correctly mapped to the user's entry DN but immediately after
that slapd crashes. (Can't grab a useful backtrace with the installed
Both machines are identical except that one VMware machine is running on
an AMD processor where also the build was made and the other VMware
machine is running on an Intel processor where the built files were just
copied to. (This copying worked from one AMD machine to another).
So I currently suspect that there's a processor-dependent optimization
done especially in the BDB build. How can I avoid that? See the current
BDB build script below. Any other suspectible compile time option?
Many thanks in advance.
------------------------------ snip ------------------------------