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.supextension.
- In theIntel InspectorGUI, in theTargettab of theProject Propertiesdialog box, setSuppressionstoApply suppressions.
- Open an existing result for the project (collected using theIntel InspectorGUI or command line interface).Outcome: In theCode LocationsandProblemspanes, theIntel Inspectormarks (strikes through) all result datapotentiallyimpacted 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 theIntel InspectorGUI or command line interface.Outcome: TheIntel Inspectordoes not collect result data impacted by suppression rules in the handwritten file and the rules in other files and directories identified in theSuppressionstab of theProject Propertiesdialog 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.supextension.
- In theIntel InspectorGUI, in theTargettab of theProject Propertiesdialog box, setSuppressionstoApply suppressions.
- Run a new analysis using theIntel InspectorGUI or command line interface.Outcome: TheIntel Inspectordoes not collect result data impacted by suppression rules in the handwritten file and the rules in other files and directories identified in theSuppressionstab of theProject Propertiesdialog 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.