Intel® Inspector User Guide for Windows* OS

ID 767798
Date 7/13/2023
Public
Document Table of Contents

Dialog Box: Project Properties-Target

(One way) To access this Intel Inspector dialog box:

  • From the Visual Studio* menu, choose Project > Intel Inspector <version> Project Properties....

    NOTE:
    In Visual Studio* 2022, Intel Inspector provides lightweight integration. You can configure and compile your application and open the standalone Intel Inspector interface from the Visual Studio for further analysis. All your settings will be inherited by the standalone Intel Inspector project.
  • From the Standalone Intel Inspector GUI menu, choose File > Project Properties....

Use this dialog box to:

Use This

To Do This

Inherit settings from Visual Studio* project checkbox and field

Visual Studio* IDE only:

  • Populate all basic settings from the Visual Studio* property pages of the StartUp project (Configuration Properties > Debugging).

  • Disable the basic settings section of the dialog box.

Microsoft* runtime environment drop-down list

  • Automatically detect the Microsoft* runtime environment based on binary executable type (choose Auto).

  • Potentially speed up collection by excluding application managed code from inspection (choose Native only).

  • Potentially speed up collection by excluding application native code from inspection (choose Managed only).

  • Inspect all code, regardless of whether it is native or managed (choose Mixed).

NOTE:

  • Microsoft .NET* 3.5 software support is deprecated in the Intel Inspector and will be removed after August, 2020. This deprecation does not apply to the Intel® VTune™ Profiler. See Release Notes for details.

  • During threading analysis, the Intel Inspector analyzes both native and managed code.

  • During memory analysis, the Intel Inspector analyzes only native code. If you choose Mixed, there is no analysis of the managed portion of your code.

  • During threading or memory analysis, the Intel Inspector supports interactive debugging only for pure native applications. If you choose Mixed or Managed only, the debug options are disabled.

Store result... radio buttons, path fields, Browse button, and Result location read-only field

  • Save results in result directories in the default location (select the Store result in the project directory radio button).

  • Save results in result directories in a custom location (select the Store result in (and create link file to) another directory radio button, and identify the custom location).

NOTE:

Change the cross-project result name template to the change the result name shown in the Result location field.

Suppressions radio buttons

  • Not collect result data impacted by the suppression rules in files and directories specified in the Suppressions tab of the Project Properties dialog box (choose Apply suppressions).

  • Ignore all suppression rules (choose Do not apply suppressions).

Child application field

Inspect a file that is not the starting application. For example: Inspect an .exe file (identified in this field) called by a script (identified in the Application field).

Enable collection progress information checkbox

Display thread activity during collection to confirm the application is still executing.

Modules radio buttons, Modify button, and field

Potentially speed up collection by limiting application module(s) for inspection. You can limit by inclusion or exclusion. For example, you can:

  • Inspect specific modules and disable inspection of all other modules (click the Include only the following module(s) radio button and choose the modules).

  • Disable inspection of specific modules and inspect all other modules (click the Exclude the following module(s) radio button and choose the modules).

NOTE:

By default, the Intel Inspector inspects all modules in the application.