...

Normally, error reports are displayed on the UNIX stderr I/O stream. See See Viewing Results on WindowsUnix for information about sending output to Insra. If you wish to send both your program’s output and the Insure++ reports to a file, you can use the normal console redirection method.

...

The error_format option only takes effect if the Insure++ errors are being reported to the console or a file. If the errors are being sent to Insra, the error format in Insra will stay the same. For details on how to change where errors are sent, see Viewing Results on WindowsUnix.

Displaying Process Information

...

You can extend the error reports generated by Insure++ to include timestamps of errors occurrences. Add the %d and/or %t characters to the error report format as specified in the advanced configuration options (Windows) or your .psrc file (Unix).

For example, the following format includes a timestamp in the generated report:

...

By default, Insure++ only reports the first error of any given kind at a source line, but you can configure Insure++ to display additional occurrences of the same errors. For Windows, modify the Report Limit field in the Reports tab of the Insure++ Control Panel to specify how many times additional errors are displayed. For Unix systems, use the Use the insure++.report_limit <number> option to your .psrc file to specify how many times additional errors are displayed. 

...

Normally, Insure++ remembers the directory in which each source file was compiled and looks there when trying to display lines of source code in error messages. Occasionally your source code will no longer exist in this directory, possibly because of some sophisticated “build” or “make” process.

You can use add the source_path option in your  advanced configuration (Windows) or to your .prsc file in your the current HOME directories (Unix) directory to provide Insure++ with an alternative list of directories to search for source code:

Windows example:

source_path .;c:\users\boswell\src;c:\srcUnix example:

source_path .:/users/me/src:/src

...

• A bug summary which lists all outstanding bugs according to their error codes.
• A leak summary which lists all memory leaks - that is, places where memory is being permanently lost.
• An outstanding summary which lists all outstanding memory blocks - that is, places where memory is not being freed, but is not leaked because a valid pointer to the block still exists.
• A coverage summary which indicates how much of the application’s code has been executed.

...

...

• .

Bugs Summary

You can include the this report summary by adding the insure++.summarize bugs option to your .psrc file and re-running your program. 

...