As part of its normal operation, Purify generates, and subsequently handles, a number of access violations. If your debugger is set to Stop always on access violations, it will display a first-chance exception whenever an access violation occurs.
There are two ways to resolve the problem:
§ Set the debugger to stop only for access violations that are not handled. Select Debug > Exceptions in Visual Studio 6 and set Access Violation to Stop if not handled.
§ If you have a reason for stopping on handled access violations, add the option /AvoidIsBadReadPtr=yes to the Purify options. This causes Purify to use an alternative, slower, method of processing that avoids stops on the handled access violations that Purify generates. To add this option, open the Default Settings or Executable Settings dialog box, or click Settings in the Run Program dialog box.. In the Files tab in the settings dialog box, type in the option in the Additional options field. Then rerun your program under Purify.
(C) Copyright IBM Corporation 1992, 2010.