Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Build tested: 389-ds-base-1.4.2.4-7.module+el8.2.0+5670+0b8b1c2e (rebuild with ASAN)
Server doesn't crash, no ASAN error is produced. Marking as VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1703
Build 389-ds-base-1.4.2.4-6 fails with ==6974==WARNING: AddressSanitizer failed to allocate 0x3040000ecdd08 bytes ==6974==AddressSanitizer's allocator is terminating the process instead of returning 0 ==6974==If you don't like this behavior set allocator_may_return_null=1 ==6974==AddressSanitizer CHECK failed: ../../../../libsanitizer/sanitizer_common/sanitizer_allocator.cc:216 "((0)) != (0)" (0x0, 0x0) #0 0x7f139130f1f6 (/lib64/libasan.so.5+0xfb1f6) #1 0x7f139132c55d in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/lib64/libasan.so.5+0x11855d) #2 0x7f13913152fc (/lib64/libasan.so.5+0x1012fc) #3 0x7f1391315347 (/lib64/libasan.so.5+0x101347) #4 0x7f139123d575 (/lib64/libasan.so.5+0x29575) #5 0x7f139123bf6a (/lib64/libasan.so.5+0x27f6a) #6 0x7f1391303b3e in __interceptor_malloc (/lib64/libasan.so.5+0xefb3e) #7 0x7f138d8049bf in __glob_lstat_compat (/lib64/libc.so.6+0x1659bf) #8 0x7f13912750b1 in glob (/lib64/libasan.so.5+0x610b1) #9 0x7f137e85ea8e in bdb_start (/usr/lib64/dirsrv/plugins/libback-ldbm.so+0x140a8e) #10 0x7f137e82bf6b in ldbm_back_start (/usr/lib64/dirsrv/plugins/libback-ldbm.so+0x10df6b) #11 0x7f1390e5e983 (/usr/lib64/dirsrv/libslapd.so.0+0x1bb983) #12 0x7f1390e65563 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1c2563) #13 0x55bac4637d8e (/usr/sbin/ns-slapd+0x2dd8e) #14 0x7f138d6c26a2 in __libc_start_main (/lib64/libc.so.6+0x236a2) #15 0x55bac463a06d (/usr/sbin/ns-slapd+0x3006d) Looks like the build is missing https://pagure.io/389-ds-base/c/cf849cc Moving to ASSIGNED.