This section provides information you need to make choices about exactly how you want Purify to gather data. It gives specific language-related instructions for using Purify to monitor code, as well as instructions for collecting analysis data using automated tests.
To learn about |
See |
The role of debug data in error-checking native-compiled Visual C/C++ programs |
How Purify Uses Relocation, Debug, and Symbol Data (Error Detection) |
The locations where Purify can find debug data for native-compiled Visual C/C++ programs |
|
Instructions for running native-compiled Visual C/C++ programs with Purify |
|
How to control the data collection levels and determine what code is monitored |
|
How to collect analysis data from the command line and in tests and test suites |
(C) Copyright IBM Corporation 1992, 2010.