使用Microsoft Visual C++来检测和隔离内存泄漏（Use Microsoft Visual c + + to detect and isolate memory leaks）.doc

使用Microsoft Visual C++来检测和隔离内存泄漏（Use Microsoft Visual c + + to detect and isolate memory leaks） Use Microsoft Visual c + + to detect and isolate memory leaks Introduction to the The ability to allocate and release memory dynamically is one of the key features of C/C + + programming languages, but the most powerful and vulnerable are the Chinese philosophers grandchildren. This is certainly true for C/C + + applications, and memory management errors are usually one of the origins of bugs. One of the most subtle and hard-to-detect bugs is the memory leak - the inability to correctly allocate allocated memory. A only a minor memory leak may not attract attention, but the leak too much memory or increasing the program may show signs of leakage, from the poor (and slowly decrease) performance to out of memory and complete failure. Even worse, a leaky program might take up a lot of memory to cause another program to fail, leaving users with nothing to do with the problem. In addition, a serious memory leak may even be a sign of other problems. Fortunately, the Visual c + + debugger and CRT libraries provide you with a range of tools for detecting and identifying memory leaks. This article explains how to use these tools to effectively and systematically isolate memory leaks. Set up memory leak detection The basic tools for detecting memory leaks are debuggers and CRT debug heap functions. To use the debug heap function, you must include the following instructions in your program: # define _CRTDBG_MAP_ALLOC # include stdlib. H # include CRTDBG. H The # include instructions must be specified in order. If you change the order, the functions you use may not work properly. The _malloc_dbg and _free_dbg containing crtdbg.h will map malloc and free functions to beta, which can track memory allocation and release. This mapping occurs only in one test system (that is, only when _DEBUG is defined). The released system USES the usual malloc and free functions. Define the low-lev