Some versions merely detect the existence of such a leak, which they report back to you when the program terminates. You're then pretty much on your own in trying to find out where and why the leak occurs. Other runtime debuggers are able to detect exactly which line of source code actually caused the memory to leak, and are thus much easier to use to solve this type of problem. A very useful thing to know about your application is how much memory it is allocating. This may allow you to find unusual problems or to optimize memory usage in ways that improve your products.
Most runtime debuggers are able to print reports of dynamic memory use.
You should investigate how this is done and how various types of memory are accounted for. Tools that display this information graphically are especially helpful. One of the virtues of runtime debuggers is that they are typically much easier to use than conventional tools. However, you should try to understand the options available for checking your code with a runtime tool. Some runtime debuggers require that you simply re-link your application in order to begin detecting problems.