§ Use Purify's PowerCheck tab to focus on the modules that are of most interest to you, while applying minimal instrumentation for error checking to those of less interest.
§ Purify's default error detection is based on the size of each module in your program and the availability of debug data and relocation data. However, you can customize error detection for each module.
§ The availability of relocation data, debug line data, and symbol data affects the level at which Purify can perform instrumentation. For more information, click
§ Collect coverage data for each run to make sure that you're searching all your code for errors.
§ You can pre-instrument libraries that are eventually loaded by LoadLibrary, to save time when you instrument and run a program, by dragging and dropping a library file (.dll) onto the Purify main window.
§ You can run an instrumented program as a system service. For more information, click
§ You can run an instrumented program outside of Purify by ensuring that the Purify cache directory is in your Path environment variable.
§ You can drag and drop an executable file (.exe) onto the Purify main window to start instrumenting and running the program. You can also drag and drop a Purify error data file (.pfy) onto the main window to open the data file.
Notes:
§ If you use Purify integrated with Visual Studio for error detection in native-compiled programs, use the Run Program dialog box to launch your program.
§ 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.