This section describes how to view runtime errors reported by Insure++. In this section:
The Insra module is Insure++'s GUI for displaying memory leaks, uncaught exceptions, and bugs reported by Insure++.
Insra shows the following types of error messages reported by Insure++:
| Icon | Description |
|---|---|
| Bug |
| Summary report When the program exits normally, Insure creates summary reports that link to the report pages. |
| Memory leak |
| Uncaught exception |
The Insure++ menu contains items the perform actions in Insra and other Insure++ interfaces.
Run instrumented applications (see Sending Messages to Insra) and exit Insure++.
Use common operating system functions.
Change how Insra displays information.
Choose an option displaying how messages are summarized.
Choose an option for sorting messages.
Choose which Insure++ interfaces to display. You can choose the following:
Depending on the type of summary report you are viewing, the following buttons may appear in the toolbar:
Error messages are grouped in the left panel by application execution session. You can click on a session or message to view additional information in the details panel. Active sessions are flagged with a yellow icon (also see Status Bar).
The top-right panel shows the session header and error message details.
Click on a session in the Sessions and Error Messages Panel to view the following session details:
Click on a message in the Sessions and Error Messages Panel to view message details, which includes the following information:
_OVERFLOW)You can click on a stack trace to launch an editor for viewing and correcting the indicated line of code. For more information, see Viewing Source Files.
Message headers will also appear for various summary reports generated by Insure++. These reports are generated using options in the Reports tab of the Insure++ Control Panel. See Report Summaries for more information. Double-clicking on a message header will open up the message window for the error or summary report selected.
You can view the corresponding source code for a particular error message by clicking on a line in the stack trace. The sources is displayed in lower-right panel. You can click on the error type icon to open the source file in your editor. In most cases, the file and line number associated with a given message have been transmitted to Insra. If Insra is unable to locate the source file, a dialog box will appear requesting that you indicate the correct source file.
Insra must know the name of your editor and the command line syntax in order to display the correct file and line from the original source code, as well as open the source file in your editor.
Insra obtains this information by reading the Advanced Option value:
visual <editor_command>
This value may contain the special tokens %f and %l, which represent the file name and line number, respectively.
The bottom of the Insra frame is the status bar.
During compilation/runtime, Insure++ makes a connection to Insra each time an error is detected. The status bar reports the number of error messages currently displayed and the number of active connections. An active connection is denoted by a yellow star to the left of the session header. A connection remains active as long as the program is compiling/running. Insra will not allow you to delete a session header as long as its connection remains active, and you may not exit Insra until all connections have been closed.
Applications instrumented with Insure++ will automatically send runtime errors to Insure. If Insra is not yet running, it will automatically start. Once the connection is established, a session header and all corresponding message headers will be reported in the order they were detected. Each new compilation or program, with its own session header and messages, will be displayed in the order in which it connected to Insra.
You can also use the Insra UI to run instrumented executables.
The application will run and any errors detected will be reported in Insra.
You can suppress errors that you do not plan to immediately address from the Insra UI.
The error will continue to be reported until fixed, but it will be suppressed from the default view. See Viewing Suppressions for information about reviewing suppressed errors.
By default, applying a suppression hides the error from view, but you can expose suppressed errors by choosing View > Suppressed Messages from the main menu or by clicking the View Suppressions button in the toolbar. Suppressed messages will appear in the UI and will be slightly grayed-out.
The Suppressions screen shows all available error messages and enables you to choose which errors to always suppress. The screen also provides an interface for removing existing suppressions.
Choose Window > Suppressions from the main menu to open the Suppressions screen.
You can perform the following actions:
Once error messages have been read and analyzed, the user may wish to clear them from the window. The Delete button on the Insra toolbar allows you to remove error messages from the display as errors are corrected in your code. A message or an entire session may be removed from the display by selecting an entry in the message header area and clicking the Delete button. A message can also be deleted by selecting Messages> Delete from the menu bar.
The following sections detail the most common errors encountered when using Insra. If you still encounter trouble after trying one of the following solutions, or if you encounter a different symptom from those listed below, contact the Parasoft Quality Consulting department. See Contacting Parasoft for more information.
While compiling or running, your program seems to hang when error output is directed to Insra and Insra is not yet running.
Run Insra manually by running the insgui.exe file located in the <INSURE_INSTALL>/bin directory.
Insra did not find your source editor on the path if you receive one of the following errors:
***Error while attempting to spawn browser execvp failed!
Warning: unable to open editor
Make sure that this application is in a directory that is on your path or that you call it with its complete pathname.