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

Re: (ITS#3414) HEAD segfaults after sasl-regexp statement



quanah@stanford.edu wrote:

>Full_Name: Quanah Gibson-Mount
>Version: HEAD
>OS: Solaris 8
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (171.66.182.82)
>
>
>
>line 51 (sasl-regexp uid=service/(.*),cn=stanford.edu,cn=gssapi,cn=auth
>ldap:///cn=Service,cn=Applications,dc=stanford,dc=edu??sub?krb5PrincipalName=service/$1@stanford.edu)
>/usr/local/etc/openldap/slapd.conf: line 51: Segmentation fault
>
>/usr/local/etc/openldap/slapd.conf: line 51:
>Program received signal SIGSEGV, Segmentation fault.
>0xfedb3218 in strlen () from /usr/lib/libc.so.1
>(gdb) bt
>#0  0xfedb3218 in strlen () from /usr/lib/libc.so.1
>#1  0xfee06520 in _doprnt () from /usr/lib/libc.so.1
>#2  0xfee086f8 in vsnprintf () from /usr/lib/libc.so.1
>#3  0xff2fa8b4 in lutil_debug (debug=-4267472, level=-4267576, fmt=0xff2fa934
>"@") at debug.c:83
>  
>
That's because "sasl", a catch-all for sasl related config directives, 
has an argument number of 2; this triggers a fake error message which is 
passed a NULL pointer.  Oc ourse, on Lnux this is not an issue... need 
to fing a clean solution.

p.





    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497