Count per-test valgrind leaks and show in report #8
Conversation
This file contains hidden or 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
cjwaldeck
force-pushed
the
cw-leak-count
branch
from
479b1b8 to
0ea8622
Compare
When libscu-c is compiled with valgrind support, add ability to count
leaked memory based on SCU_VALGRIND_LEAK_LEVEL set using memcheck's
own definitions:
[0 - none, 1 - leaked, 2 - dubious]
Default is set to 1 - leaked.
VALGRIND_DO_QUICK_LEAK_CHECK is used as it corresponds to
'--leak-check=summary'. Since we are not interested in the specifics
of where the leaks are this should suffice.
Fail test cases where leaks of the set level are present.
cjwaldeck
force-pushed
the
cw-leak-count
branch
from
0ea8622 to
b24b344
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When libscu-c is compiled with valgrind support, add ability to count
leaked memory based on SCU_VALGRIND_LEAK_LEVEL set using memcheck's
own definitions:
[0 - none, 1 - leaked, 2 - dubious]
Default is set to 1.
VALGRIND_DO_QUICK_LEAK_CHECK is used as it corresponds to
'--leak-check=summary'. Since we are not interested in the specifics
of where the leaks are this should suffice.
Fail test cases where leaks of the set level are present.