To avoid investigating the same issues over and over again, set the

Intel Inspector

to propagate state information from a baseline result the first time you open a new result.

By default, the

Intel Inspector

propagates state information from the immediately previous result of the same analysis type. However, you may need to configure the

Intel Inspector

to propagate state information from a specific earlier result. This is most appropriate if your source code is undergoing branched development. You can also instruct the

Intel Inspector

to not propagate states from a baseline result, which sets the state of all issues in a new result to

New

.

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

.

You can control - at a cross-project level - how the

Intel Inspector

names future results and result directories. For example, you may choose a cryptic name for results you consider temporary and plan to delete, or you may choose a more descriptive name for long-term audit purposes.

When you run an analysis on an application, the

Intel Inspector

executes that application. You can send application output to the:

Collection Log
window
Separate console window

When you run an analysis configured for interactive debugging, the

Intel Inspector

halts application execution and, depending on how the analysis was started, launches a debugging session immediately or when a problem is detected. By default, the

Intel Inspector

launches the GNU gdb* debugger. You can choose from several debuggers.