Setting Runtime Checking Options

The RunTime Memory Checking tab on the Debug Executable, the Configure Current Debugged Session, and Edit Debug Target dialog boxes lets you specify the following runtime checking options for your C, C++, or Fortran executable.

  • Access Checking. Turns on memory access checking.
  • Do Not Stop On Access Errors. By default, runtime checking stops execution of your program each time it encounters an error. You can ask runtime checking to continue running the program.
  • Suppress Duplicate Error Messages. By default, runtime checking suppresses duplicate error messages. You can choose to have it report every error encountered, even if the error is a duplicate
  • Continue runtime checking in an exec'ed process. By default, runtime checking is not performed on a child process. You can specify that you want runtime checking to continue when a child process is started with the exec() function. The runtime checking settings of the program calling exec() are passed on to the child process.
  • Maximum Errors To Report. By default, runtime checking reports a maximum of 1000 errors. You can specify the number of errors you want runtime checking to report.
  • Skip Memory Checking For Loadobjs. By default, all load objects are included in memory checking. After you have started your debugging session, you can use this setting to exclude a specific load object from memory checking. In the Configure Current Debugged Session dialog box, click the browse button for this setting and select the Skip Memory Checking checkbox for the load object in the Skip Memory Checking for Loadobjects dialog box.
  • Check Memory Usage and Leak. Turns on memory usage and leak checking
  • Number of Frames Used for Matching. By default, runtime checking combines stack traces for all memory usage and memory leaks in one report if the call stack at the time of allocation for two or more leaks matches this number of frames. The default value is 3 for C++, 2 otherwise.
  • Maximum Number of Frames. By default, the number of distinct frames displayed when reporting memory usage and memory leaks is 8 or the number of frames used for matching.
  • Automatic Block Report At Exit. By default, runtime checking generates a block report when your program exits. You can tell it not to generate this report.
  • Automatic Leaks Report At Exit. By default, runtime checking generates a leaks report when your program exits. You can tell it not to generate this report.

  • Legal Notices