This section provides information and instructions for running native-compiled Visual C/C++ code in the specific environments that Purify supports.
To learn about |
See |
Instructions for running programs in the Purify standalone user interface |
Running a Program in the Purify Standalone Interface (Error Detection) |
Instructions for running programs the from the command line |
|
How to attach a debugger to a program running under Purify |
|
How to start a debugger with Purify |
|
How to set breakpoints in programs running under Purify |
|
How to get precise-level Purify data when you check the release version of a program |
Checking the Release Version of a Visual C++ Program (Error Detection) |
How to check a child process under Purify |
|
How to have Purify check a C++ system service |
|
How to run an in-proc COM server under Purify |
|
How to run an out-of-proc COM server under Purify |
|
Saving time when your program runs under Purify by instrumenting modules in advance |
|
Changing the default file name for the instrumented version of a program |
Changing the File Name of Instrumented Programs (Error Detection) |
How to have Purify use a different cache directory |
Changing the Cache Directory for Instrumented Programs (Error Detection) |
Checking the instrumentation log for a program run |
|
Checking the runtime environment and settings that were in effect for a program run |
(C) Copyright IBM Corporation 1992, 2010.