CODEWITHSUNDEEP
c
greywanderer
greywanderer

Reputation: 31

warning for not using free() malloc

Are there any safeguards built into GCC that check for memory leaks? If so how can I use them? When I compile with "gcc -Wall -o run run.c", the compiler does not seem to care if any allocated heap-space is being freed at the end of the code. I could not find any simple fixes for this on Google.

Thanks much for your time.

EDIT: Google Searches did point to Valgrind among other tools. But I was curious as to why the compiler cant deal with this issue. As a newbie, it seemed a simple enough task to check if every "malloc" has a "free" associated with it.

Upvotes: 3

Views: 536

Answers (2)

jim mcnamara
jim mcnamara

Reputation: 16389

There are two ways to analyze code for problems - static analysis and run-time analysis. Static analysis reads the code - this is what compilers do really well. Run-time analysis for code problems happens when the code is linked against another set of libraries that see what the code actually does as it runs under surveillance. Finding memory leaks is difficult for static analysis but not for a run-time analysis package.

Other run-time analyses are things like code coverage - does all parts of your code run? gcov does this, like valgrind and electric fence look for memory problems like leaks.

So, no, there are no really good compiler safeguards for testing memory leaks.

Upvotes: 3

HolyBlackCat
HolyBlackCat

Reputation: 96335

There is -fsanitize=leak GCC flag.

It overrides malloc/calloc/free to make them count allocated and freed blocks of memory.
If your program is compiled with this flag, it prints information about detected leaks to the terminal after execution.

You can read about it here and here.

Also, I have never used it, so this answer is completely based on GCC manual.

Upvotes: 0

Related Questions