The first step in Purify'ing your native-compiled Visual C/C++ code is to instrument and run the program.
§ To use Purify in Visual Studio, collect error and coverage data for native-compiled code by using the Run Program dialog box.
§ To use Purify standalone, run the program using Purify's Run Program dialog box.
Purify instruments your code so that it can perform error detection and optionally collect coverage data for the run.
Purify provides a default level of error detection for each component, but you can use the PowerCheck tab in the settings dialog boxes to set the level of instrumentation you want. You can also set options to control things such as whether Purify records and displays Uninitialized Memory Copy (UMC) messages and the length of call stacks recorded for errors and allocations.
During instrumentation, Purify makes copies of the executable and its associated modules, and uses Object Code Insertion (OCI) technology to insert into the code the instructions it will use to detect errors and monitor coverage. Purify shows you its progress as it instruments the executable file and modules.
After instrumentation, Purify starts the program and, as you exercise the instrumented program, displays a Data Browser window with an Error View for the run and reports detailed diagnostics about the run-time errors it detects.
When you exit the program, Purify reports memory leaks. You can specify additional settings to have Purify also report memory in use and handles in use at exit.
If you collected coverage data for the run, Purify displays the data in the coverage tabs in the Data Browser window.
Note:
§ If you are using Microsoft Windows 2000 or higher, the Windows File Protection feature (WFP) may cause problems when you use Purify's /replace command line option. For a workaround to this problem, click .
(C) Copyright IBM Corporation 1992, 2010.