Dialog Box: Create Suppression
- Although you are ultimately trying to suppress problems, theIntel Inspectorvehiclefor defining a suppression rule is one or more code locations.
- Narrow rules suppress a limited number of relevant problems; wider rules suppress a greater number of relevant problems.
- Every rule applied during analysis adds processing time.
- The goal: Suppress the greatest number of relevant problems with the fewest number of rules.
- To review rules to be applied during analysis, check theSuppressionstab of theProject Propertiesdialog box.
- To apply rules during analysis, select theApply Suppressionsradio button on theTargettab of theProject Propertiesdialog box.
- A code location may be part of multiple problems; therefore, multiple rules may suppress the same code location, or a rule created to suppress one problem may partially impact another problem.
To Do This
Add a short description to distinguish the new rule from other rules.
Save indrop-down list and
Choose a non-default location only to make the rule easily accessible to others.
Problem typedrop-down list
Code Location Descriptioncheckboxes
A single code location with all but one characteristic set to
* (any)is ideal for widening a rule to suppress the greatest number of relevant problems.
Code Location Descriptiondrop-down lists
There are three
Code Location Descriptionpossibilities:
Deallocation site, and
* (any). Memory error example: If you right-click a
Mismatched allocation sitecode location for an occurrence of a
Mismatched allocation/deallocationproblem, the
Intel Inspectordisplays one code location marked
Allocation siteand one code location marked
* (any); you can click the drop-down arrow to change
* (any). Threading error example: If you right-click a
Readcode location for an occurrence of a Read/Write
Data raceproblem, the
Intel Inspectordisplays two code locations marked
* (any)and does not provide drop-down arrows.
Number of Frames in Rulefields
Identify the current number of stack frames that are the focus of the rule.
Start Frame in Rulefields
Identify the last-called stack frame that is currently the focus of the rule.
It may take some time for all strikethroughs to appear.