Immediately before your program finishes executing, MemoryScape halts the program. This lets you examine memory state information at that time.

Stopping program execution when the program stops is optional. You can use a MemoryScape option that lets your program finish executing. If you do this, however, MemoryScape discards the state information associated with the program. (For information on changing this option, see Task 3: “­Setting MemoryScape Options”.)

MemoryScape allows you to halt your program’s execution at any time. However, it does not allow you to select the exact code location for your program to stop, and the program may stop inside a malloc or new call. If this happens, you may see an odd corrupt guard block or leak in your reports. When your process resumes execution, it will clear up the odd result.

If you require fine program control using breakpoints, or you need thread control, you will need to use TotalView with MemoryScape. See Debugging with TotalView in the Locating Memory Problems section of this documentation.