AW: Problems with ldapwhoami -> slapd -> segmentation fault

["Guus Leeuw jr." <Guus-Leeuw@gmx.de>]

> -----Ursprüngliche Nachricht-----
> Von: owner-openldap-software@OpenLDAP.org 
> [mailto:owner-openldap-software@OpenLDAP.org] Im Auftrag von 
> Tony Earnshaw
> Gesendet: woensdag 25 augustus 2004 12:31
> An: Openldap list
> Betreff: Re: Problems with ldapwhoami -> slapd -> segmentation fault
> 
> 
> ons, 25.08.2004 kl. 08.12 skrev Guus Leeuw jr.:
> 
> > I don?t really know whether the question actually belongs 
> here (*it* 
> > seems to be indicating a problem in the Cyrus SASL arena), but then 
> > again, the problem only shows with slapd (2.2.15 and cvs HEAD).
> [...]
> 
> >  
> > <==slap_sasl2dn: Converted SASL name to cn=guus leeuw 
> > (test),ou=people,dc=junior,dc=homenet
> > getdn: dn:id converted to cn=guus leeuw 
> > (test),ou=people,dc=junior,dc=homenet
> > slap_sasl_getdn done
> > SASL Canonicalize 2 [conn=0]: slapAuthcDN="cn=guus leeuw 
> > (test),ou=people,dc=junior,dc=homenet"
> > /etc/sasldb2
> > Segmentation fault
> > [root@jupiter slapd]#
> >  
> > So now the big thing is:
> > How come? ;)
> 
> segfaults (SIGVSEG) with SASL are most often caused by the 
> compile linking in SASL1 libs along with SASL2. Do an ldd (or 
> strings if you've linked statically) on slapd to ensure that 
> this isn't the case.

Following is the output:
[leeuwg@jupiter slapd]$ ldd slapd | grep -i sasl2 | grep -i lib
        libsasl2.so.2 => /opt/cyrus-sasl/lib/libsasl2.so.2 (0x400cf000)
[leeuwg@jupiter slapd]$ ldd slapd | grep -i sasl1 | grep -i lib
[leeuwg@jupiter slapd]$ strings slapd | grep -i sasl2 | grep -i lib
libsasl2.so.2
[leeuwg@jupiter slapd]$ strings slapd | grep -i sasl1 | grep -i lib
[leeuwg@jupiter slapd]$ 

So, having it done thoroughly, this is not the point... Any other
suggestions?

Guus

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004