Hello,

I've built openldap 2.4.45 on a CentOS 7.4.1708 machine with the following 
configuration:

./configure --enable-bdb=no --enable-hdb=no --enable-mdb --with-tls=openssl 
--enable-spasswd --enable-syslog --enable-modules --enable-cleartext 
--enable-overlays --enable-accesslog --enable-auditlog --with-threads 
--enable-shared --enable-ldap --enable-monitor --enable-deref --enable-slapd 
--enable-ppolicy --enable-memberof

When I run make test I receive numerous segmentation faults:

output from make test:

> ./scripts/test028-idassert: line 252: 28923 Segmentation fault      (core 
> dumped) $SLAPD -f $CONF1 -h $URI1 -d $LVL $TIMING > $LOG1 2>&1
> >>>>> test028-idassert completed OK for mdb.
> 
> >>>>> Starting test029-ldapglue for mdb...
> running defines.sh
> ### This test requires the ldap backend and glue overlay.
> ### If available, and explicitly requested, it can use SASL bind;
> ### note that SASL must be properly set up, and the requested
> ### mechanism must be available.  Define SLAPD_USE_SASL={yes|<mech>},
> ### with "yes" defaulting to DIGEST-MD5 to enable SASL authc[/authz].
> Using proxyAuthz with simple authc...
> Running slapadd to build slapd database...
> Starting local slapd on TCP/IP port 9011...
> Starting remote slapd 1 on TCP/IP port 9012...
> Starting remote slapd 2 on TCP/IP port 9013...
> Using ldapsearch to check that slapd is running...
> Using ldapsearch to check that slapd is running...
> Using ldapsearch to check that slapd is running...
> Testing ldapsearch as uid=bjorn,ou=People,dc=example,dc=com for 
> "dc=example,dc=com"...
> Filtering ldapsearch results...
> Filtering original ldif used to create database...
> Comparing filter output...
> Testing ldapsearch as anonymous for "dc=example,dc=com"...
> Filtering ldapsearch results...
> Filtering original ldif used to create database...
> Comparing filter output...
> >>>>> Test succeeded
> ./scripts/test029-ldapglue: line 222: 28992 Segmentation fault      (core 
> dumped) $SLAPD -f $CONF1 -h $URI1 -d $LVL $TIMING > $LOG1 2>&1
> ./scripts/test029-ldapglue: line 222: 28994 Segmentation fault      (core 
> dumped) $SLAPD -f $CONF2 -h $URI2 -d $LVL $TIMING > $LOG2 2>&1
> ./scripts/test029-ldapglue: line 222: 28996 Segmentation fault      (core 
> dumped) $SLAPD -f $CONF3 -h $URI3 -d $LVL $TIMING > $LOG3 2>&1
> >>>>> test029-ldapglue completed OK for mdb.


In /var/log/messages:

> Oct 11 09:31:42 www kernel: slapd[9039]: segfault at 1100fffff7 ip 
> 00007febd7a2f4dc sp 00007ffe832541f8 error 4 in 
> libc-2.17.so[7febd79af000+1b8000]
> Oct 11 09:31:42 www kernel: slapd[8997]: segfault at 1100fffff7 ip 
> 00007f48923e44dc sp 00007ffec5a22658 error 4 in 
> libc-2.17.so[7f4892364000+1b8000]
> Oct 11 09:31:42 www kernel: slapd[8975]: segfault at 1100fffff7 ip 
> 00007f01a727d4dc sp 00007ffd9a127698 error 4 in 
> libc-2.17.so[7f01a71fd000+1b8000]
> Oct 11 09:31:42 www abrt-hook-ccpp: Process 8975 (slapd) of user 0 killed by 
> SIGSEGV - ignoring (repeated crash)
> Oct 11 09:31:42 www abrt-hook-ccpp: Process 9039 (slapd) of user 0 killed by 
> SIGSEGV - dumping core
> Oct 11 09:31:42 www abrt-hook-ccpp: Process 8997 (slapd) of user 0 killed by 
> SIGSEGV - dumping core


I don't see any obvious problems with the linked libraries:

[me@here openldap-2.4.45]# ldd servers/slapd/slapd
        linux-vdso.so.1 =>  (0x00007ffd98751000)
        libltdl.so.7 => /lib64/libltdl.so.7 (0x00007f930d78b000)
        libicuuc.so.50 => /lib64/libicuuc.so.50 (0x00007f930d412000)
        libicudata.so.50 => /lib64/libicudata.so.50 (0x00007f930be3d000)
        libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f930bc20000)
        libssl.so.10 => /lib64/libssl.so.10 (0x00007f930b9ae000)
        libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f930b54c000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f930b332000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f930b116000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f930ad52000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f930ab4e000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f930a846000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f930a543000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f930a32d000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f930a0f6000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f9309ea8000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f9309bc0000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f93099bc000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f9309788000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f9309572000)
        /lib64/ld-linux-x86-64.so.2 (0x000055eefaf24000)
        libfreebl3.so => /lib64/libfreebl3.so (0x00007f930936e000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f9309160000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f9308f5c000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f9308d34000)
        libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f9308ad2000)


Any advice or suggestions would be welcome.

Regards,
Scott




Reply via email to