[Date Prev][Date Next] [Chronological] [Thread] [Top]

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.


They love us, don't they, They feed us, won't they,
Oh who will think a boy and bear
Could be well accepted everywhere?
It's just amazing how fair people can be

mail: tonye@billy.demon.nl