Rational Purify is a runtime analysis product that detects runtime errors in native-compiled (unmanaged) Visual C/C++ applications, and profiles memory usage of managed applications developed for Microsoft's .NET Framework.
You can use Purify:
§ integrated with Microsoft Visual Studio (all .NET languages, including managed Visual C++)
§ in the Purify standalone user interface (all languages)
§ from the command line (all languages)
§ in test harnesses and scripts, using the Purify command line options (all languages)
This help system provides information you need to get started with runtime error detection and memory profiling, as well as information for using the more advanced features of Purify.
To learn about |
See |
What you need to know as a beginning user of Purify |
|
Using Purify to detect runtime errors in native compiled Visual C/C++ code, or to profile the memory usage of .NET applications |
|
Troubleshooting information and special cases |
|
Purify windows, dialog boxes, and toolbars |
Additional information that applies not only to Rational Purify but also to Rational Quantify and Rational PureCoverage is included in the PurifyPlus books.
To learn about |
See |
API functions for controlling data collection programmatically |
|
Reference information for Purify, including keyboard and mouse shortcuts, Purify files, and recommended settings for using Purify in Visual Studio |
|
Technical terms used in the Purify user interface and help system |
Notes:
§ Purify uses Byte Code Insertion (BCI) technology to instrument .NET managed code dynamically in memory. Purify does not display the Instrumentation progress dialog box, and it does not save copies of BCI instrumented code.
§ Purify uses Object Code Insertion (OCI) technology to instrument copies of native-compiled (unmanaged) executables and associated modules, and saves the instrumented copies in its cache directory. Purify displays the Instrumentation progress dialog box as it instruments native-compiled code.
(C) Copyright IBM Corporation 1992, 2010.