wolfgang.hummel@hp.com wrote:

We managed to install it with debug-symbols now, but did not have a new crash (yet).

However we did a deeper anaylysis of existing crashes. Here is the outcome:

#0 0x00000037a4e30045 in raise () from /lib64/libc.so.6 (gdb) thread apply all bt

Thread 3 (process 17892): #0 0x00000037a5a075a5 in pthread_join () from /lib64/libpthread.so.0 #1 0x000000000043402c in slapd_daemon () at ../../../servers/slapd/daemon.= c:2834 #2 0x0000000000420d75 in main (argc=3D5, argv=3D0x7fff3a6ee4b8) at ../../.= ./servers/slapd/main.c:953

Thread 2 (process 17894): #0 0x00000037a5a0a496 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/lib= pthread.so.0 #1 0x000000000052fdab in ldap_pvt_thread_pool_destroy (tpool=3D0x8635e8, r= un_pending=3D487320688) at ../../../libraries/libldap_r/tpool.c:558 #2 0x000000000043767c in slapd_daemon_task (ptr=3D<value optimized out>) a= t ../../../servers/slapd/daemon.c:2764 #3 0x00000037a5a062e7 in start_thread () from /lib64/libpthread.so.0 #4 0x00000037a4ece3bd in clone () from /lib64/libc.so.6

Thread 1 (process 17895): #0 0x00000037a4e30045 in raise () from /lib64/libc.so.6 #1 0x00000037a4e31ae0 in abort () from /lib64/libc.so.6 #2 0x00000037a4e681bb in __libc_message () from /lib64/libc.so.6 #3 0x00000037a4e6f444 in _int_free () from /lib64/libc.so.6 #4 0x00000037a4e72a6c in free () from /lib64/libc.so.6 #5 0x0000000000559e07 in sb_rdahead_remove (sbiod=3D0x2aaac488d0d0) at ../= ../../libraries/liblber/sockbuf.c:606 #6 0x0000000000559fb9 in ber_sockbuf_free (sb=3D0x2aaac488d0d0) at ../../.= ./libraries/liblber/sockbuf.c:71 #7 0x0000000000000000 in ?? ()

This is quite unlikely to be a valid trace, since sb_rdahead_remove is only used on UDP sockets, and UDP socket support is not enabled by default nor is there a configure switch to enable it.