Hello, First of all I'd say that most likely this segfault is a result of badly designed application and/or bad coding. The segfault occurs while this application tries to move an entry to non-existing LDAP container. Unfortunately I don't have access to the source code of this app. The segfault is below with backtrace from dgb: ns-slapd[4983]: segfault at 18 ip 00007f2ed4a60759 sp 00007f2e955e13e0 error 4 in libback-ldbm.so[7f2ed4a34000+8f000] #0 0x00007f2ed4a60759 in id2entry_add_ext () from /usr/lib64/dirsrv/plugins/libback-ldbm.so #1 0x00007f2ed4a8a34c in modify_update_all () from /usr/lib64/dirsrv/plugins/libback-ldbm.so #2 0x00007f2ed4a8eb4f in ldbm_back_modrdn () from /usr/lib64/dirsrv/plugins/libback-ldbm.so #3 0x00007f2eddbecdaa in ?? () from /usr/lib64/dirsrv/libslapd.so.0 #4 0x00007f2eddbed66c in do_modrdn () from /usr/lib64/dirsrv/libslapd.so.0 #5 0x0000000000413904 in ?? () #6 0x00007f2edc0369e3 in ?? () from /lib64/libnspr4.so #7 0x00007f2edb9d9851 in start_thread () from /lib64/libpthread.so.0 #8 0x00007f2edb72711d in clone () from /lib64/libc.so.6 I'd appreciate any thoughts regarding what kind of (bad) things this application is doing. Is it possible to have a kind of protection in this case on directory server? Regards, Vlad. -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
