Intel Inspector

offers the following states:

Intel Inspector

propagates state information from the baseline result when it determines an issue in a new result corresponds to an issue in the baseline result. For example, if you set the state for a problem in the baseline result to

Not a Problem

, the

Intel Inspector

sets the state for the corresponding problem in the new result to

Not a Problem

.

The only exception: If you set an issue state to

Fixed

in the baseline result but the issue still appears in the new result, the

Intel Inspector

sets the issue state to

Regression

in the new result.

Use the

Intel Inspector

filtering to focus on issues in specific states. For example, in the

Filters

pane on the

Summary

window:

In the
Investigated
category, choose
Not investigated
to reduce clutter by displaying only issues with a state of
New
,
Not fixed
, or
Regression
.
In the
State
category, choose
Confirmed
to review issues that are - or should be - reported in your bug tracking system.
In the
State
category, choose
New
to concentrate on issues introduced since the last analysis run.
In the
State
category, choose
Regression
to verify all issues marked as
Fixed
in the baseline were successfully fixed.
In the
State
category, choose
Not a problem
to double-check earlier conclusions that no fix is needed.

When you change the state of a problem set, the

Intel Inspector

responds by similarly changing the state of all problems currently in the problem set.

In scenarios where a problem set contains problems with different states (such as when source code changes introduce a new instance of a problem previously set to a non-new state), the

Intel Inspector

assigns the most severe state to the problem set according to this hierarchy:

Regression
(most severe state)
New
Not Fixed
Confirmed
Fixed
Not a Problem
Deferred
(least severe state)