User Guide

  • 2020
  • 09/09/2020
  • Public Content
Contents

Choosing Problems

During analysis, the
Intel Inspector
displays problems in the order detected in the
Problems
pane.
After analysis is complete, the
Intel Inspector
:
  • Groups problems detected during analysis into problem sets
    (but still provides visibility into individual problems and problem occurrences)
    .
  • Prioritizes the items in the
    Problems
    pane.
  • Offers filtering to help you focus on those items that require your attention. For example, you can temporarily limit the items displayed in the
    Problems
    pane by:

About Prioritization

Intel Inspector
assigns problems a severity level:
Critical
( Critical severity icon 
			 ),
Error
( Error severity icon 
			 ) and
Warning
( Warning severity icon 
			 ). The severity indicates the seriousness of the defect.
Problem sets inherit the severity of the problems they contain. The
Intel Inspector
prioritizes problem sets first by severity and then by number of code locations. Problem sets containing more code locations precede those containing fewer.
Think of this prioritized list of items on the
Problems
pane as a
to-do
list. Start at the top and work down.

About Filtering by Inclusion

Use the
Intel Inspector
filtering function to temporarily limit the items in the
Problems
pane to only those problem sets containing problems that meet specific criteria.
For example, you can filter the list to show only those problem sets containing problems...
  • With
    Investigated
    =
    Not investigated
    to show only problem sets with a state of
    New
    ,
    Not fixed
    , or
    Regression
    (that is, hide the problem sets you have already investigated)
  • Or with
    State=Not fixed
    and
    Severity
    =
    Error
  • Or with
    State=Not fixed
    and
    Severity
    =
    Error
    and
    Type
    =
    Data Race
  • Or in a specific file

About Filtering by Exclusion

Use the
Intel Inspector
filtering function to temporarily set aside occurrences of the same, possibly false positive, items en masse in the
Problems
pane. For example:
  1. In the
    Investigated
    category in the
    Filters
    pane on the
    Summary
    window, choose
    Not investigated
    to display only problems with a state of
    New
    ,
    Not fixed
    , or
    Regression
    .
    If this is the first result of this analysis type, or if you chose the
    Do not get problem states from another result
    option on the
    State Management
    page of the product
    Options
    dialog box during startup, all problems have a state of
    New
    .
  2. Click the
    Sort
    drop-down list in the
    Filters
    pane and choose
    Sort by Item Count
    to sort remaining problems by count in descending numerical order.
  3. In the
    Type
    category in the
    Filters
    pane, choose the problem type with the highest item count to display only those problems in the
    Problems
    pane.
  4. Click on any problem in the
    Problems
    pane, then press Ctrl+A to select all problems.
  5. Right-click any of the selected problems to display a context menu, then choose
    Change State
    Not a Problem
    to change the state of all selected problems.
  6. In the
    Type
    category, click the
    All
    button to deselect problem criteria.
  7. Repeat steps 3 - 6 for each problem type with many occurrences.
  8. Start working the remaining problems.
Be aware that when you temporarily set aside problems en masse, you may inadvertently set aside a problem of interest. For example, if you are not responsible for problems in source file A and you:
  1. Use the filtering function to select all problems in source file A.
  2. Set the state for all problems in source file A to
    Not a problem
    .
Some of these problems may touch more than one source file. When you filter on a source file, you filter on all problems intersecting that source file. The fact that a problem has some intersection with a file for which you are not responsible does not mean the problem does not concern you.
However if you are responsible for source files A, B, and C, you can filter first to source file A, then to source file B, then to source file C. You may see some problems more than once, but you will ultimately investigate all problems in files for which you are responsible.

About Filtering by a Set of Source Files

Use the
Intel Inspector
filtering function to temporarily limit the items in the
Problems
pane to those from a set of source files.

Product and Performance Information

1

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804