It then reports wherever memory and other resources were allocated but never freed, a common source of program failure-and often one that's difficult to track down. When Memory Sleuth finds an error, it shows the programmer exactly where in their source code the error starts. Entirely new user interface makes working with Memory Sleuth easier. Automatically extends bug checking to any DLLs that the main program uses. Optionally filters known and often harmless - compiler bugs from its reports Helps programmers focus on important problems in their own code, not leaks in the VCL or MFC frameworks.
Filters are user extensible, too.
Helps new users configure just the right settings for their analysis. Supports all major Borland and Microsoft development systems for Windows One product, nothing extra to buy. It requires no source code changes to work. New documentation Memory Sleuth 2 ships with online help and a new 75-page manual, which is provided as an Adobe Acrobat file. The new manual fully explains Memory Sleuth operation and also includes a useful overview of common programming mistakes and how to avoid them.