This section describes the types of suppression that are available:
You must specify which type of error to suppress. You can specify which parts of the program to suppress. The options are:
The default; applies to the whole program
Applies to an entire load object, such as a shared library, or the main program
Applies to all functions in a particular file
Applies to a particular function
Applies to a particular source line
Applies to a particular instruction at an address
By default, runtime checking suppresses the most recent error to prevent repeated reports of the same error. This setting is controlled by the dbx variable rtc_auto_suppress. When rtc_auto_suppress is set to on (the default), a particular access error at a particular location is reported only the first time it is encountered and suppressed thereafter. This setting is useful, for example, for preventing multiple copies of the same error report when an error occurs in a loop that is executed many times.
You can use the dbxenv variable rtc_error_limit to limit the number of errors that will be reported. The error limit is used separately for access errors and leak errors. For example, if the error limit is set to 5, then a maximum of five access errors and five memory leaks are shown in both the leak report at the end of the run and for each showleaks command you issue. The default is 1000.