#51058 AddressSanitizer: odr-violation
Closed: wontfix by mreynolds. Opened by vashirov.

Issue Description

I'm running ASAN build on F32, have these errors while creating an instance:

=================================================================
==259067==ERROR: AddressSanitizer: odr-violation (0x55c85bcb3020):
  [1] size=4 'slapd_ldap_debug' ldap/servers/slapd/tools/pwenc.c:37:5
  [2] size=4 'slapd_ldap_debug' ldap/servers/slapd/libglobs.c:143:5
These globals were registered at these points:
  [1]:
    #0 0x7f403a4f1cc8  (/lib64/libasan.so.6+0x37cc8)
    #1 0x55c85bcaf30c in __libc_csu_init (/usr/bin/pwdhash+0x530c)
  [2]:
    #0 0x7f403a4f1cc8  (/lib64/libasan.so.6+0x37cc8)
    #1 0x7f403aea97e1 in call_init.part.0 (/lib64/ld-linux-x86-64.so.2+0x117e1)
==259067==HINT: if you don't care about these errors you may set ASAN_OPTIONS=detect_odr_violation=0
SUMMARY: AddressSanitizer: odr-violation: global 'slapd_ldap_debug' at ldap/servers/slapd/tools/pwenc.c:37:5
==259067==ABORTING
=================================================================
==259097==ERROR: AddressSanitizer: odr-violation (0x7f1881b3f180):
  [1] size=8 'attr_newsuperior' ldap/servers/plugins/retrocl/retrocl_po.c:34:13
  [2] size=8 'attr_newsuperior' ldap/servers/slapd/auditlog.c:29:7
These globals were registered at these points:
  [1]:
    #0 0x7f1886175cc8  (/usr/lib64/libasan.so.6+0x37cc8)
    #1 0x7f1886b247e1 in call_init.part.0 (/lib64/ld-linux-x86-64.so.2+0x117e1)
  [2]:
    #0 0x7f1886175cc8  (/usr/lib64/libasan.so.6+0x37cc8)
    #1 0x7f1886b247e1 in call_init.part.0 (/lib64/ld-linux-x86-64.so.2+0x117e1)
==259097==HINT: if you don't care about these errors you may set ASAN_OPTIONS=detect_odr_violation=0
SUMMARY: AddressSanitizer: odr-violation: global 'attr_newsuperior' at ldap/servers/plugins/retrocl/retrocl_po.c:34:13
==259097==ABORTING

Package Version and Platform

389-ds-base-1.4.4.1-20200429git0f446a549.fc32.x86_64

Steps to reproduce

  1. Build 389-ds-base with ASAN
  2. setup-ds.pl

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: normal
- Issue set to the milestone: 1.4.1

The retrocl code was fixed but not pwdhash/pwenc

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.4 (was: 1.4.1)

This was fixed in https://pagure.io/389-ds-base/pull-request/51193

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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/4111

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