Should I remove Debugging Tools for Windows x64 by Microsoft Use Debugging Tools for Windows to debug drivers, applications, and services on Windows systems. How to Use the Citrix Symbol Server to Obtain Debug Symbols. How to Use the Citrix Symbol Server to Obtain Debug Symbols. How to find memory leak in a C codeproject Answering the second part of your question, Is there any standard or procedure one should follow to ensure there is no memory leak in the program. Yes, there is. And this is one of the key differences between C and C. In C, you should never call new or delete in your user code. RAII is a very commonly used technique, which pretty much solves the resource management problem. Every resource in your program a resource is anything that has to be acquired, and then later on, released file handles, network sockets, database connections, but also plain memory allocations, and in some cases, pairs of API calls Begin. Microsoft Visio 2007 Iso. IMG_500174.jpg' alt='Umdh Windows 7 Download' title='Umdh Windows 7 Download' />XEnd. X, Lock. Y, Unlock. Y, should be wrapped in a class, where the constructor acquires the resource by calling new if the resource is a memroy allocationthe destructor releases the resource,copying and assignment is either prevented by making the copy constructor and assignment operators private, or are implemented to work correctly for example by cloning the underlying resourceThis class is then instantiated locally, on the stack, or as a class member, and not by calling new and storing a pointer. You often dont need to define these classes yourself. The standard library containers behave in this way as well, so that any object stored into a std vector gets freed when the vector is destroyed. So again, dont store a pointer into the container which would require you to call new and delete, but rather the object itself which gives you memory management for free. Likewise, smart pointer classes can be used to easily wrap objects that just have to be allocated with new, and control their lifetimes. This means that when the object goes out of scope, it is automatically destroyed, and its resource released and cleaned up. If you do this consistently throughout your code, you simply wont have any memory leaks. Everything that could get leaked is tied to a destructor which is guaranteed to be called when control leaves the scope in which the object was declared. Sorry, page not found Please enable cookies and refresh the page.