How to locate Linux memory leaks

2.For illustrative convenience, write a memory leak **, apply 1024 bytes, and do not release.

3.Compile gcc -o test to generate an executable program.

4.Using the valgrind test, the command is as follows.

The location of LIN NUX memory leaks can be solved by the amount of memory and traffic.

Oops: How to locate memory leaks? In the case of memory leakage, there should be a positioning function for positioning, and it will be prompted step by step according to its positioning function.

If this thing is a memory leak, this thing can't be located, and if it is operated and maintained, this thing belongs to you.

This is actually very simple, we know that you only need normal positioning, in fact, it is completely fine.

In this case, you must use some detection solution, only then can you do this, and in exceptional cases, some instruments can also do this.

How memory leak locates this should be called some news about this memory.

Not so good, went to operate today.

This needs to be detected to be locatable, after all, you need to pay attention to memory leaks.

Check it out and find the problem easily.

How to locate a memory leak? I don't know what kind of this?

In fact, memory has nothing to do with its positioning, right?

Thanks, how to position? I don't know how to talk about it, you can check it out when the time comes, and they will tell you where he is.

A memory leak is a situation where a program fails to release memory that is no longer in use due to an oversight or error.

This is one of the nightmares for C and C++ programmers.

1) Substance: Memory leak does not mean that the memory physically disappears, but that after the application allocates a certain piece of memory, due to a design error, it loses control of the memory before it is released, resulting in a waste of memory;

2) Principle: The key to memory leakage is to record the allocated memory and the operation of releasing memory to see if it can match. Track the lifecycle of each piece of memory;

3) Method: Different development environments have different detection methods, which are introduced below with VisualStudio as an example.

When used in VS, it needs to be added.

#define _crtdbg_map_alloc

#include

The role is to map the malloc and free functions to their debug versions malloc dbg and free dbg, which will keep track of memory allocation and release (valid in debug versions).

crtdumpmemoryleaks（）；

The function will show the current memory leak, that is, the memory leak when the program runs to this line**, and all undestroyed objects will report the memory leak, so let this function be put to the end as much as possible.

Linux can use Valgrind to detect memory leaks.