Red Hat Bugzilla – Bug 830353
valgrind reported memleaks and mem errors
Last modified: 2013-02-21 03:17:55 EST
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/313 1) the ldbm instance dse preop delete callback deletes the entry and dn caches - some other plugins called after this attempt to access those caches 2) normalize_mods2bvals allocs the berval twice in the dn syntax case 3) mep_parse_config_entry allocs value but does not free it 4) dna_be_txn_pre_op can goto bail: in certain cases and attempt to free NULL smods
please add steps to verify this bugzilla
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Request you to add steps to verify bugzilla.
1) setup the directory server to run under valgrind 2) run the managed entry and DNA tests from TET 3) the valgrind output should not report leaks or errors in normalize_mods2bvals(), mep_parse_config_entry(), dna_be_txn_pre_op()
Created attachment 690426 [details] Valgrind output Verified on 389-ds-base-1.2.11.15-11.el6.x86_64
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. http://rhn.redhat.com/errata/RHSA-2013-0503.html