Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR is aiming to solve a memory leak that happens to be located in the LDAP module (see bug #3190).
Details
The memory leak concerns the exported methods ldap_write_result and ldap_result_check when a regexp is used for substringing the result.
Solution
The subst_expr* that is allocated for the methods ldap_write_result and ldap_result_check is never freed.
In order to fix it, we declare the fixup_free_substre function that is used in the definition of the "free_fixup" function for the subst_expr parameter of these two functions.
Compatibility
This change is not compatible with versions prior to the commit 4137c5a ldap: port script functions to new param interface
Additional data
Hereafter is the memory allocation table that led me to discover this leak :