Here is the full stacktrace of this segfault: http://pastebin.com/ReqQU3mM
Regards,
Vlad.
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
I wasn't able to reproduce this segfault using CentOS:
Name: 389-ds-base
Arch: x86_64
Version : 1.2.9.14
Release : 1.el6
However, when I updated to
Name: 389-ds-base
Arch: x86_64
Version : 1.2.10.2
Release : 20.el6_3
I've got the same segfault. I'll
On 11/14/2012 02:05 AM, Vladimir Elisseev wrote:
Obviously, I've tried ldapmodify and, as expected, it ends with an
error, no segfaults. However, I just tried
ldapmodrdn -r -h localhost -p 389 -D "cn=xxx" -W
"cn=0207,ou=1,ou=Users,ou=132252,ou=Tenants,dc=CIDS" "cn=020
(2012/11/13 05:22), Rich Megginson wrote:
On 11/13/2012 03:30 AM, Vladimir Elisseev wrote:
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 LD
