Stumbled across an issue where tests on a particular part of a codebase were passing OK, however the function left a dangling reference to a file pointer open. So it occurs to me that there may be some benefit in having an additional option to run successful tests through an additional layer of Memory Leak testing.
A program known as valgrind seems to easily accommodate this kind of test and is readily available on most Unix systems.
Stumbled across an issue where tests on a particular part of a codebase were passing OK, however the function left a dangling reference to a file pointer open. So it occurs to me that there may be some benefit in having an additional option to run successful tests through an additional layer of Memory Leak testing.
A program known as
valgrindseems to easily accommodate this kind of test and is readily available on most Unix systems.