User Guide

Quick Start
Side Panel
Output Window
Graph View
App Toolbar
Launch Dialog
Connect Dialog
Snapshot Toolbar
Full Snapshot
Snapshot Views
Call Tree View
Call Tree Grouping
Memory View
Functions View
Types View
Leaks View
Tools Toolbar
Subtract Snapshots
Rewind Memory
VMem View
Settings Toolbar
Symbol Paths Dialog
MemPro Unix/GCC
PureDev Logo MemPro logo
C++ Memory Profiler



History Path While MemPro is connected and collecting allocations it stores all allocations in a file in disk. As you can imagine, this file can get quite big. Please ensure that you have plenty of disk space available. You can change the path that MemPro will save the history file here. MemPro will reuse the same history file for each session. When you save a mempro file you have the option of embedding the history file.
Units Changes the units that the GUI used. Can be GB, MB, K or bytes. Most places that show a memory value will use these units. You can also changes the units using the units button on the GUI.
Embed Allocs file in save files The allocs file is another name for the history file. If this is checked MemPro will embed the allocs file in the mempro save files. If the allocs file is huge then MemPro will warn you to verify that you really do want to embed it.
Embed pdb file in save files MemPro can embed pdb files into mempro save files. This is useful because it means that you don't have to keep the pdb files for each mempro file. If this is checked MemPro will embed the pdb files by default. Pdb files can take up a lot of memory, so if they are above a certain size, MemPro will still warn you and let you choose not to embed them.
Check for updates If this is checked MemPro will check with the PureDev Software servers to see if a newer version of MemPro is available for download. If it is you will be prompted to download and installed the new version.


Launch Exe, args and working directory These settings mirror the Launch Dialog settings. The settings are saved so that you don't have to enter them each time you run MemPro.


Connect IP and Port These settings mirror the Connect Dialog settings, with the addition of the secondary port. If MemPro can't connect on the default port (27016), it will try the secondary port. This can be useful when debugging on more than one machine. The settings are saved so that you don't have to enter them each time you run MemPro.


Callstack Filters Symbols in callstacks that match these wildcards are removed and not shown in the Call Tree view. Useful for removing the MemPro tracking functions and new/delete calls. * are automatically added to the start and end of each entry.

© Copyright 2011 - 2013 Stewart Lynch