Visible to Intel only — GUID: GUID-79DA3C72-5DCD-4E90-BA7E-F2734EDC5325
Visible to Intel only — GUID: GUID-79DA3C72-5DCD-4E90-BA7E-F2734EDC5325
Typical Suppressions Usage Models Using Handwritten Suppression Files
There are two typical usage models for handling handwritten suppression files in the Intel Inspector. They differ depending on how you want to confirm the effectiveness of the files:
Apply the handwritten file to an existing result, check the resulting strikethrough marks, then continue editing the file in the text editor as necessary.
Apply the handwritten file to a new result, check the result for problems that should have but did not vanish, then continue editing the file in the text editor as necessary.
These usage models also apply to editing suppression files already created using the Intel Inspector GUI or command line interface.
Apply the File to an Existing Result
Create the handwritten file using a text editor. Save the handwritten file to the default suppression directory for the project. Use the default .sup extension.
In the Intel Inspector GUI, in the Target tab of the Project Properties dialog box, set Suppressions to Apply suppressions.
Open an existing result for the project (collected using the Intel Inspector GUI or command line interface).
Outcome: In the Code Locations and Problems panes, the Intel Inspector marks (strikes through) all result data potentially impacted by the rules in the handwritten file. (It may take some time for all marks to appear. The marks remain in the result even if you close and then reopen the result.)
Review the marked data to assess the effectiveness and potential reach of the rules in the handwritten file. If necessary, continue editing the handwritten file in the text editor.
Repeat steps 3 and 4 as necessary.
Run a new analysis using the Intel Inspector GUI or command line interface.
Outcome: The Intel Inspector does not collect result data impacted by suppression rules in the handwritten file and the rules in other files and directories identified in the Suppressions tab of the Project Properties dialog box.
Apply the File to a New Result
Create the handwritten file using a text editor. Save the handwritten file to the default suppression directory for the project. Use the default .sup extension.
In the Intel Inspector GUI, in the Target tab of the Project Properties dialog box, set Suppressions to Apply suppressions.
Run a new analysis using the Intel Inspector GUI or command line interface.
Outcome: The Intel Inspector does not collect result data impacted by suppression rules in the handwritten file and the rules in other files and directories identified in the Suppressions tab of the Project Properties dialog box).
Review the remaining problems in the result to assess the effectiveness and potential reach of the rules in the handwritten file. If necessary, continue editing the handwritten file in the text editor.
Repeat steps 3 and 4 as necessary.