Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add memory leak tests #33

Open
PeterHamilton opened this issue Jan 31, 2020 · 0 comments
Open

Add memory leak tests #33

PeterHamilton opened this issue Jan 31, 2020 · 0 comments
Labels
testing Testing updates, fixes, and configuration

Comments

@PeterHamilton
Copy link
Contributor

Add another set of tests (that mirror existing ones) but run through Valgrind, like this:

valgrind -v --leak-check=full ./tests

The expected output should ultimately be something like:

==12384== HEAP SUMMARY:
==12384==     in use at exit: 0 bytes in 0 blocks
==12384==   total heap usage: 516 allocs, 516 frees, 13,873 bytes allocated
==12384== 
==12384== All heap blocks were freed -- no leaks are possible
==12384== 
==12384== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==12384== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

The test should verify that no leaks are possible.

@PeterHamilton PeterHamilton added the testing Testing updates, fixes, and configuration label Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Testing updates, fixes, and configuration
Projects
None yet
Development

No branches or pull requests

1 participant