Use the Advanced tab in the Default Settings dialog box to specify when to check for new memory leaks, and at what interval you want Purify to perform late detect scans in all native-compiled (unmanaged) programs. By default, the interval is set to 0 and Purify does not perform late detect scans.
You can specify information such as the number of seconds you want Purify to wait, the number of heap operations you want the program to perform, and the number of seconds you want to elapse before Purify reports memory corruption.
These are the main controls in the dialog box:
Notes:
§ Purify does not perform late detect scans unless:
§ You select Enable late detect scans.
§ You call the Purify API function PurifySetLateDetectScanCounter or PurifySetLateDetectScanInterval in your program code. This will temporarily enable late detect scans at the interval you specify for the remainder of the program run.
§ You call the Purify API function PurifyHeapValidate in your program code, or you select View > Memory API Functions > HeapValidate... in the user interface. This will perform an on-demand validation, but it will not enable interval late detect scans.
§ When Purify discovers errors from a leak scan, it generates Memory Leak (MLK) or Potential Memory Leak (MPK) messages in the Error View.
§ When Purify discovers errors from a late detect scan, it generates Late Detect Array Bounds Write (ABWL) or Late Detect Free Memory Write (FMWL) messages in the Error View.
(C) Copyright IBM Corporation 1992, 2010.