#48289 389-ds-base: ldclt-bin killed by SIGSEGV
Closed: wontfix Opened by nhosoi.

Description of problem:
This problem also exists on RHEL-7.

ldclt-bin -b "ou=people,dc=example,dc=com" -w password -e esearch,randombindd

n,randombinddnlow=10,randombinddnhigh=99,randomattrlist=cn:sn:uid:ou:telephoneN
umber:facsimileTelephoneNumber:mobile:roomNumber -n 100 -I 32 -r 1 -R 9999 -f
"uid=guestXX" -s subtree
ldclt version 4.23
Segmentation fault (core dumped)

gdb /usr/bin/ldclt-bin core.14929

...
(gdb) bt

0 0x00007f6ec5fd7811 in __strlen_sse2 () from /lib64/libc.so.6

1 0x00007f6ec7990371 in parseFilter (src=0x0, head=head@entry=0x7f6ec7ba0b48

,
tail=tail@entry=0x7f6ec7ba0b50 ,
ndigits=ndigits@entry=0x7f6ec7ba0b40 )
at ldap/servers/slapd/tools/ldclt/ldclt.c:1225

2 0x00007f6ec7990b19 in basicInit () at

ldap/servers/slapd/tools/ldclt/ldclt.c:1441

3 0x00007f6ec798753d in main (argc=19, argv=0x7fffc77f6898) at

ldap/servers/slapd/tools/ldclt/ldclt.c:3169

Version-Release number of selected component:
389-ds-base-1.3.3.1-13.el7


Patch provided: https://bugzilla.redhat.com/attachment.cgi?id=1036892

The patch was provided by Stanislav Zidek in bz1229799

Created attachment 1036892 [details]
Patch fixing the issue

Reviewed by nhosoi and pushed to master:
79aa178..5b33c78 master -> master
commit 5b33c781d2568c930a0856f0a42c1e1d53e3358f

Pushed to 389-ds-base-1.3.4:
48308f3..8cd610a 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
commit 8cd610a944daf72a41e5b35065f8b363f8154f28

Pushed to 389-ds-base-1.2.11:
aa59677..49d0ef6 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 49d0ef667441e009af071fd0f4d48f31f3514063

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.5 backlog

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1620

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

Metadata