Feature: Ignore defined functions from leak detection #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cyrus-jackson
changed the title
added 3 commits
December 8, 2022 15:43
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a new feature to ignore the defined functions in
vld.inifrom checking for memory leak detection.Currently vld does not have a direct way to assess
static stringallocations, even though the destruction gets called at exit vld reports it as a leak. With this feature, the function name (after manual introspection, ofcourse) can be added toIgnoreFunctionsListinvld.iniand the stack containing the function will not be reported for leaks.This is especially useful in cases where there are false positives in third party libraries and with this it can be ignored.