Process Event by Event

Use this screen to obtain more information on events. These events can occur because MemoryScape is notifying you either that a memory event occurred (see “Task 6: Using Run-time Events” for more information) or that your program raised an untrapped condition.

There are two ways to view process events: by process, or by event, as shown below. The By Process screen shows similar information. This report is useful if you are analyzing multiple processes stopped at different events.

MemoryScape remembers the events that occur within your program. Select the event you wish to obtain information about by clicking on it here.

Tells you about the event or the problem.

Selecting this tab displays a page showing the backtrace, source file, and source code surrounding the place where the event occurred.

Selecting this tab displays a page showing the backtrace, source file, and source code surrounding the place where your program allocated the memory block. Not all events have this information. For example, if your program tried to free stack memory, there would not be block allocation information.

Selecting this tab displays a page showing the backtrace, source file, and source code surrounding the place where your program deallocated the memory block. For example, Not all events have this information.

Selecting this tab displays a page with a visual display of just this block as well as some additional information.

Contains the backtrace associated with the event, allocation, or deallocation. A backtrace is the call stack that existed when your program allocated the memory block.

The source area shows the line in your program associated with the information shown in the backtrace area.

Shows the line in your program associated with the information shown in the backtrace area. When you click on a function in the backtrace area, the information in this area changes.

Shows all of the processes stopped at the same event. Select a process in this list to see the event details below.

Tells MemoryScape to open the currently selected process in TotalView. The TotalView process window will display the current state of that process. You must have a TotalView license available to debug in TotalView.

Be aware that opening the TotalView process window from within MemoryScape does not initialize TotalView in the same way as starting TotalView directly. The definitions in your .tvdrc file and your saved breakpoints are not loaded. However, you can load a breakpoint file using the Action Point menu item in the process window. If you need the definitions in your .tvdrc file, start TotalView first and open MemoryScape from within TotalView.