Debugging Memory Problems with MemoryScape : Chapter 2 Memory Tasks : Task 4: Controlling Program Execution

Task 4: Controlling Program Execution
This task shows you how to control the execution of your program from within MemoryScape. After you’ve told MemoryScape which programs it should debug, you must tell it to let them begin executing. As your program executes, MemoryScape collects memory information. For long- running programs, you will want to start execution, stop it, look at memory information, and then continue execution.
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”.
Before reading this task, you should be familiar with the following:
Chapter 1, “Locating Memory Problems”
Contains an overview of memory concepts and MemoryScape.
Task 1: “Getting Started”
Tells you how to start MemoryScape. It also contains an overview of the kinds of information you can ­obtain.
Task 3: “­Setting MemoryScape Options”
Describes how to configure MemoryScape so that it performs the activities you want it to perform.
The controls for starting and stopping program execution are contained in the Home | Summary screen and the lower left corner of many screens. You will find additional controls in the Manage Process and Files screen, Figure 52.
 
 
Topics within this task are:
*
*
*
*

Rogue Wave Software, Inc.
Voice: (303) 473-9118
rwonlinedocs@roguewave.com