Intel® Inspector 2018 Release Notes - Windows* / Linux*

ID 672221
Updated 11/13/2017
Version Latest



Intel® Inspector 2018 helps developers identify and resolve memory and threading correctness issues in their C, C++ and Fortran applications on Windows* and Linux*. Additionally, on Windows platforms, the tool allows the analysis of the unmanaged portion of mixed managed and unmanaged programs and identifies threading correctness issues in managed .NET C# applications.

Intel Inspector is a dynamic error checking tool for developing multithreaded applications on Windows* or Linux* operating systems. Intel Inspector maximizes code quality and reliability by quickly detecting memory, threading, and source code security errors during the development cycle. You can also use the Intel Inspector to visualize and manage Static Analysis results created by Intel compilers in various suite products. Intel Inspector is an easy, comprehensive solution that delivers rapid results by isolating memory and multithreading errors.

Intel Inspector has a standalone graphical user interface (GUI) as well as a command line interface (CLI). In addition, on Microsoft Windows systems, the Intel Inspector integrates into the Microsoft Visual Studio* 2013 and later versions.

This document provides system requirements, installation instructions, issues and limitations, and legal information

Use the Getting Started tutorial and reference documentation to learn more about the Intel Inspector. The tutorials and documentation can also be accessed offline. For example, if you choose the default installation path, the Getting Started and Help can be found on the following paths:

Getting started:

Windows: C:\Program Files (x86)\IntelSWTools\documentation_2018\en\Inspector\welcomepage\get_started.htm

Linux: /opt/intel/documentation_2018/en/inspector/welcomepage/get_started.html

You can access the product help in a web browser by opening the index.htm in the documentation help directory.

If you did not register this product during installation, do so at the Intel® Software Development Products Registration Center. Registration entitles you to free technical support, product updates and upgrades for the duration of the support term.

For Technical Support, Product Updates, User Forums, FAQs, tips and tricks, and other support information, visit the support page.

Note: If your distributor provides technical support for this product, contact them for support rather than Intel® Corporation.

What's New

Intel® Inspector 2018 Update 1

  • Introduced an enhanced Getting Started Guide
  • Fixed some issues with the Microsoft Visual Studio* 2017 integration
  • Fixed some issues with profiling on a system with an Antivirus enabled
  • Bug fixes

Intel® Inspector 2018

  • Support for C++17 std::shared_mutex and Windows SRW Locks, that enable threading error analysis for applications with read/write synchronization primitives.
  • Support for cross-OS analysis to all license types. The installation packages for additional operating system can be downloaded from the Intel® Software Development Products Registration Center.
  • Support and integration in Microsoft Visual Studio* 2017
  • Support for Intel® Xeon® Scalable Processors.
  • Support for Microsoft Windows Server* 2016.
  • Support for Fedora* 26
  • Support for Ubuntu* 17.04
  • Support for SUSE* Linux Enterprise Server* 12 SP2
  • Support for Debian* 9
  • Bug fixes

System Requirements

Supported Architectures and Terminology

Intel® Inspector supports the following architectures:


  • IA-32 Architecture refers to systems based on 32-bit processors generally compatible with the Intel® Pentium® processors (such as, Intel® Pentium® 4 processor), or processors from other manufacturers supporting the same instruction set, running a 32-bit operating system.
  • Intel® 64 Architecture refers to systems based on IA-32 architecture processors that have 64-bit architectural extensions (such as, Intel® Core™2 processor family), running a 64-bit operating system. If the system is running a 32-bit operating system, then IA-32 architecture applies instead. Processors from other manufacturers supporting the same instruction set and running a 64-bit operating system are also supported.


Minimum System Requirements


  • A system based on an IA-32 or Intel® 64 architecture processor supporting the Intel® Streaming SIMD Extensions 2 (Intel® SSE2) instructions (Intel® Pentium 4 processor or later, or compatible non-Intel processor)
    • Intel® Inspector requires specific knowledge of assembly-level instructions. Its analysis may not operate correctly if a target executable contains instructions not supported by IA-32 or Intel® 64 architectures. In this case, run the analysis with a target executable that contains only supported instructions. After you finish using the Intel® Inspector, you can revert to using unsupported instructions in the target executable.
    • For the best experience, a multi-core or multiprocessor system is recommended
  • 4GB RAM
  • 350MB free disk space for all tool features and architectures
  • Supported Microsoft* operating systems (embedded editions not supported):
    • Microsoft Windows 7* SP1
    • Microsoft Windows Server* 2008 SP2 and 2008 R2 SP1
    • Microsoft Windows HPC Server 2008 and 2008 R2
    • Microsoft Windows 8* operating system
    • Microsoft Windows 8.1* operating system
    • Microsoft Windows 10* operating system
    • Microsoft Windows Server* 2012, 2012 R2 and 2016
  • Supported operating systems (embedded editions not supported):
    • Red Hat* Enterprise Linux* 6 and 7
    • CentOS* versions equivalent to Red Hat* Enterprise Linux* versions listed above
    • Fedora* 24, 25 and 26 (pangox-compat package should be installed)
    • SUSE* Linux Enterprise Server* 11, 12 and 12 SP2
    • Debian* 7, 8 and 9
    • Ubuntu* 14.04, 16.04, 16.10, 17.04
  • Supported Microsoft Visual Studio* versions:
    • Microsoft Visual Studio* 2013
    • Microsoft Visual Studio* 2015
    • Microsoft Visual Studio* 2017 including Update 3
  • Recommended compilers:
    • Intel® C/C++ Compiler XE 12.0 or higher
    • Windows: Intel® Visual Fortran Compiler XE 12.0 or higher
    • Linux: Intel® Fortran Compiler XE 12.0 or higher
    • GNU* C/C++ Compiler 3.4.6 and higher
  • Supported debuggers:
    • Intel® Composer XE 2015 debugger or later
    • GNU gdb* debugger versions 6.3 or later with working remote debugging support (there are known issues with gdb-7.1-xx.fc13 versions)
  • Application coding requirements:
    • Supported programming languages:
      • Fortran
      • C
      • C++
    • Supported threading methodologies:
      • Intel® Threading Building Blocks (Intel® TBB)
      • Win32* Threads on Windows* OS
      • POSIX* Threads on Linux* OS
      • OpenMP* (via Intel® OpenMP compatibility library on Windows. On Linux, see note below)
      • Intel® C++ Compiler parallel language extensions
      • Intel® Cilk™ Plus
      • Microsoft PPL* (via Intel® TBB)
  • Managed Application coding requirements
    • Supported programming languages:
      • C# (full support for .NET* versions between 2.0 to 3.5 inclusive)
      • C# (limited support for .NET 4.0 - see note below).
  • Sun* or Oracle* JRE 1.6 or higher is required to run Intel® Software Manager which enables automatic product updates and is one of the components of the Intel® Inspector installation.
  • PDF reader software such as Adobe* Reader* 7.0 or later for reading installed documentation



Intel® Inspector has limited support for .NET 4.0:

  • The Microsoft * Task Parallel Library classes and algorithms in the System.Threading.Tasks namespace are not supported.
  • The following synchronization class in the System.Threading namespace (new in .NET 4.0) is not supported: Barrier.


Floating licensing service requirements

Floating licenses of 2017 or 2018 version Intel® Software Development Tools require the latest version (Intel 2.5/lmgrd of Intel® Software License Manager for successful installation. For the latest version of Intel® Software License Manager, please go to the Intel® Registration Center (choose the right OS and platform; only users with floating license registrations have access to this link). For more details, see Installation Errors Related to Intel® Software License Manager Upgrade

To get started the with the Intel® Software License Manager, please refer to this tutorial: Intel® Software License Manager Getting Started

Installation Notes

This product package can be used to install the software on both IA-32 systems and Intel® 64 systems. The installer determines the system architecture and installs the appropriate files. Both 32-bit and 64-bit versions of the software are automatically installed on an Intel 64 system.

The installation of the Intel® Inspector removes any earlier installed minor version of this product (with the same major version number). Different major versions can co-exist with each other. On Windows however, only one version can be integrated with any one particular Microsoft Visual Studio* installation at a given time.

If you are installing the product for the first time, you need the product serial number or a valid license file to activate the product.

Windows instructions:

The product installation package is a self-extracting compressed executable file with one IA-32 package that you can install on either a 32-bit or 64-bit system. If downloaded, this compressed file may be located at: C:\Users\<username>\Download

To begin the installation, double-click the compressed self-extracting <package_name>_setup.exe file as a user with administrative privileges. Select the full installation option to use default install settings and get the complete set of user interfaces (includes a GUI front-end for using the Intel Inspector as well as Visual Studio integration). Activation is required.

Linux Instructions:

  1. Uncompress the package: gunzip <package-name>.tar.gz

  2. Extract the files: tar xf <package-name>.tar

  3. Start the installation. (Note: For successful installation, you should have read and write permissions for the /tmp directory.)

    • To install on a local system enter the following:

      cd <package-name>

    • ./

      Note: If you want to install the software for use by any user, you must do this as the root user. To install to a network-mounted drive or shared file system for multiple users, become the root user then enter:

      cd <package-name>


  4. Follow the prompts to complete the installation and activation of the software.


Silent Installation (Windows)

To learn details of silent non-interactive installation on Windows* systems, refer to the following link: Using Silent Non-interactive Installation on Windows* OS Systems


You must activate the product to finish installation. There are several methods for product activation:


  • Activate using a serial number. Internet connection is required.

  • Remote activation using a serial number. Use this method when your computer is not connected to the internet. You must use another computer with internet access to complete activation.

  • Activate using a license file.

  • Activate using a license server.


You can also evaluate the product for 31 days.

Intel® Software Manager

Intel® Software Manager is a utility that lets you:


  • Download and install updates for your Intel® Software Development Products.

  • Manage subscription status of installed software.

  • Activate serial numbers.

  • Find out about the latest news for Intel® Software Development Products.


Intel® Software Manager requires an Internet connection to connect to a remote server for information and updates.

Intel® Software Manager installs with Intel® Software Development Products on Windows*, Linux*, and macOS* operating systems.

To obtain more information about the Intel® Software Manager, please refer to the web page.

Default Installation Folders

The default top-level installation folder for this product is:

Windows: C:\Program Files (x86)\IntelSWTools\Inspector 2018

Linux: /opt/intel/inspector_2018

You can select a different top-level folder name as part of a custom installation.

Installing Collectors on Remote Systems

You can install the Intel Inspector collectors on a remote system after installing and activating the full product on one system. This is intended for use on systems where space or license checking is an issue. No product activation is required to install and run the collectors on a remote system, but the analysis results may not be viewed on the remote system. Result folders must be copied or made available through the network to the system where the full product was installed and activated, since the visualization of results and command-line reporting option require an activation check.

If you have the Windows installer package of Intel Inspector proceed with the following steps to install the Intel Inspector collectors on a remote Linux system:


  1. Run <package_name>_setup.exe -x to extract the installer files into the default location: C:\Users\<username>\Downloads\Intel\Inspector_2018_setup. If you need another location, use the command <package_name>_setup.exe -x -f <location>. Note : You can skip this step if you know the extraction location for the original installation.
  2. Locate and copy the folder installs\insp\insp_cli_install to the remote machine.
  3. On a remote machine, run installs\insp\insp_cli_install\Inspector.msi and follow the installer instructions.
  4. To install collectors silently, use:

    msiexec.exe -i installs\insp\insp_cli_install\Inspector.msi -qn -log <log-file>

On a Linux system, perform the following steps:

  1. Copy the CLI_install folder (found at the top level in the untarred product install package) to the remote machine.

  2. Execute the ./ script file (this file is located inside the CLI_install folder). Activation is not required.


IMPORTANT: While no activation is required to install and run collectors on a remote machine, you are still bound by the terms and conditions of the End User License Agreement in the original install and included with the collectors remote install after you install the collectors.

Activating Your Evaluation Software After Purchase

If you installed an evaluation version of Intel® Software Developer Products and then decided to purchase the product, you can use the Intel® Software Manager to enter a valid product serial number to convert your evaluation license to fully licensed status.

On Windows ,run the Intel® Software Manager from C:\Program Files (x86)\Common Files\Intel\Intel Software Manager\ism.exe.

On Linux, the Intel® Software Manager is installed on /opt/intel/ism/ism.

Be sure to login or su to root to run if you want the product license to be available to all system users.

Click Activate, and supply a valid product serial number to convert your evaluation software to a fully licensed product.

Changing, Updating or Removing the Product

On Microsoft Windows, if you want to add or remove components from an installation, open the Control Panel, select the Add or Remove Programs applet, select Intel Inspector 2018 Update X, and click Change/Remove (or Uninstall/Change in the Microsoft Windows 7* operating system).

On Linux, to remove the product, execute the following commands:

Note: Replace /opt/intel with the chosen install folder name if the default folder was not used.

  1. cd /opt/intel/advisor_2018

  2. (as a root user or the same user who performed the install)

Setting up the Intel Inspector Command Line Environment

To easily access the command line interface, use a command prompt window with the proper environment settings.

On Windows, you can open such a window from the Start menu, using a shortcut under All Programs > Intel Parallel Studio XE 2018 > Analyzers > Command Prompt.

Alternatively, you can open a command prompt window and use the following command to setup the proper environment:

C:\Program Files (x86)\IntelSWTools\Inspector 2018\inspxe-vars.bat

On Linux, you can set up the Intel Inspector environment settings in a terminal session using the following command from a bash shell:

source <install-dir>/

When using a C shell, source the .csh script instead.

Known Installation and Configuration Issues (Windows only)


  1. In very rare situations, the installer may hang during the phase Configuring integration with Microsoft* Visual Studio 20xx software… phase. If the installer hangs for more than 20 minutes, locate process devenv.exe and shut down the process. Make sure that you do not have any running instances of Visual Studio software. Reboot the machine and then install the product again.
  2. By default, Visual Studio sets the Launch in Browser option to display documentation for integrated products. To view the Intel Inspector local help documentation: Choose Help > Intel Inspector 2018 > Intel Inspector 2018 Help or use context-sensitive help. If you still encounter problems viewing the help, Choose Help > Set Help Preferences > Launch in Help Viewer.
  3. If you have problems viewing Microsoft Visual Studio help pages, check the settings for Internet Explorer in Tools > Internet Options > Security. To allow correct display of help, in the Internet zone enable MIME Sniffing and Active scripting.Alternatively, from Tools > Internet Options > Security add "about:internet" to the list of trusted sites.


Issues and Limitations

General Issues on Windows and Linux


  • On some hardware, the Intel® Inspector may report data race problems on simple operations (such as variable load or store operations) assumed to be atomic operations instead of explicit atomic instructions. In particular, the Intel Inspector reports false data race issues on C++ 11, std::atomic class operations compiled with the GNU gcc* compiler. Intel® and Microsoft* compilers use explicit atomic instructions; therefore, code generated with these compilers is not impacted.
  • Intel® does not guarantee that the Intel Inspector will detect or report every memory and threading error in an application.
    • Not all logic errors are detectable.

    • Heuristics used to eliminate false positives may hide real issues.

    • Highly correlated events are grouped into a single problem.

  • You can use the Intel Inspector to analyze applications in debug and release modes. To learn more about options necessary to produce the most accurate, complete results, refer to the following related resources:
  • If no symbols are found for a module in which a problem is detected, the Intel Inspector displays the call stack and observation source code of the first location where it can find symbols. If it cannot find any location in the call stack with symbols, it displays the module name and relative virtual address (RVA) for the location.
  • Applications that crash when run outside the Intel Inspector may crash or hang the Intel Inspector runtime analysis engine. For example, a corrupt return address on an application call stack crashes the runtime analysis engine. If a crash occurs, problems detected prior to that time can be viewed, but memory leaks will not be reported.

    Recommendation: Review the reported problems - it is likely one of them caused the crash.

  • Intel Inspector uses a socket to communicate between the graphical user interface and the runtime analysis engine. Preventing an application from opening a socket prevents an analysis of the application from being started by the graphical user interface. The command-line interface can be used to run an analysis in this case and the results can subsequently be viewed using the graphical interface.
  • Intel Inspector may report an incorrect call stack following an interruption of normal call flow, such as when an exception is thrown and caught. While the Intel Inspector recognizes and attempts to correct result data when this situation occurs, it is possible for a threading or memory problem to be reported before the call stack is fully corrected.
  • If the Intel Inspector reports insufficient memory errors while analyzing OpenMP* applications, try setting OMP_NUM_THREADS to limit the number of OpenMP threads. In most cases, OMP_NUM_THREADS=2 is sufficient.
  • If the Intel Inspector reports insufficient memory errors during analysis, try analyzing your application in sections by running several analyses and excluding a different set of modules for each run. Note: The Intel Inspector does not detect or report issues in excluded modules.
  • If a child application is selected for analysis, the Intel Inspector analyzes only the first instance of that application, even if multiple instances of that application occur.
  • When taking advantage of the Intel Inspector custom filter by source, be aware that this filter does not persist when reloading results.

Windows only General Issues:

  • To debug an application that is running an Intel Inspector analysis you must choose one of the Intel Inspector debug analysis options when starting the application. Using the Visual Studio Debugger "attach" command after starting an application under analysis does not have the same effect and will result in debugging the Inspector analysis tool and not the application. When starting a debug analysis session in the documented manner, the Intel Inspector uses a probe in the Visual Studio process to intercept and modify the Visual Studio Debugger behavior such that it controls execution and displays information about the target application rather than the analysis tool.
  • To analyze applications using Boost* on a Windows* operating system, you must compile your application and Boost libraries (for example, boost_thread-vc80-mt-gd-1_42.dll etc.) with debugging information enabled (/Zi), optimization disabled (/Od), and the C runtime library dynamically linked in. To make sure you have debugging information enabled and optimization disabled, you can download the Boost source and build the libraries yourself. The .pdb files need to be placed next to the binaries or at the location of pdb paths coded in the binaries. To learn more, see: Intel® Inspector
  • On-demand leak detection will not report memory leaks until the end of the basic block in which they occur, as there is still an internal reference in the program to that memory. If the baseline for leak detection is not reset, these leaks will be reported at the next request [200348282]
  • Intel Inspector only has limited support for Windows* fibers.
  • Inspector doesn't support binaries built with "/DEBUG:FASTLINK" option, that is default in Microsoft Visual Studio* 2015 Update 1.
  • Virus checking can sometimes interfere with our ability to instrument code. The following error indicates the virus checker has modified ntdll.dll, which will cause our collections to fail. Currently there is no workaround, except turning off the virus checker. This issue will be resolved in the next product update.

    Collection failed

    8/23/2017 1:26:10 PM Collection failed. The data cannot be displayed.

    [Instrumentation Engine]: SYSCALL_INSPECTOR: The NTDLL!NtTerminateThread function jumps out of NTDLL, at 0x7ffeb0fe00c4. It may be hooked by a PIN-incompatible software installed on the system Source\pin\base_w\ipc_server_windows.cpp: LEVEL_BASE::StartServer: 2216: assertion failed: res == TRUE

  • Your target application might crash or freeze in case when you are using one of the Intel Inspector debug analysis options in Microsoft Visual Studio* IDE running on systems with Intel® Xeon® processor E5 v2 and v3 family.
  • Intel Inspector does not support development of new Windows 8* Store Apps and use of WinRT APIs.
  • Intel Inspector supports the .NET 4.0 Runtime with the exception of the new Task Parallel Library classes.

Linux only General Issues:

  • Intel Inspector does not currently support Security-enhanced Linux* settings (SELinux); it supports only Permissive mode.

    Recommendation: Either disable SELinux (set the line "SELINUX=disabled" in your /etc/sysconfig/selinux file or add the "selinux=0" kernel argument in lilo.conf or grub.conf files) or make a SELinux mode adjustment (set the line "SELINUX=permissive" in your /etc/sysconfig/selinux file or ask your system administrator to make a SELinux mode adjustment). You may need to reboot your system after changing the system parameters. See for more information about SELinux. [200155374]

  • Intel Inspector cannot launch a debugger when the terminal type konsole is used on KDE* versions older than 4.6.

    Recommendation: Use a terminal such as xterm on older KDE versions when using the analysis with debug feature. [200223810]

  • When running a multi-threaded application, use of Enable debugger when problem detected (-appdebug=on-error) can result in multiple debugger sessions being opened. Only the first occurrence will be connected and able to debug the application under analysis. The workaround is to use Select analysis start location with debugger (-appdebug=on-start) so that only one debug session will be started and then turn on analysis by entering the extended debugger command monitor begin-analysis then continue to resume execution until it encounters a problem.
  • If you try to store results on a Parallel Virtual File System 2 (pvfs2), Intel Inspector analysis fails with the following error: "Error: Failed to create a database. Cannot continue."

    Recommendation: Specify a result directory location that is not on a pvfs2 file system. [200213391]

  • If you encounter problems searching Intel Inspector help using a certain web browser, consider using a newer version of that browser or use a different web browser as your default browser.
  • When using interactive debugging with gdb on Fortran programs on Linux, the 'next' and 'step' commands in the debugger can take a very long time to execute. Recommendation: use the Intel® debugger with Fortran programs. The launched debugger can be changed in the GUI from the File->Options menu. It can be set for the CLI using the INSPXE_DEBUGGER environment variable or the -debug-using command line option.
  • Memory and threading analysis require ptrace to be enabled on Linux platforms. Some newer Linux distributions disable it by default. Message reads, " Error: Failed to start the analysis because the scope of ptrace() system call application is limited." Recommendation: Enable ptrace by setting /proc/sys/kernel/yama/ptrace_scope to 1. [200317488]
  • The message "detected an attempt to suspend an internal thread…" happens when the target application attempts to suspend all threads, causing the Intel Inspector XE thread suspension as well. To avoid this error:
    • Disable the Enable collection progress information checkbox in the Target tab of the Project Properties dialog box.
    • Disable the Enable interactive memory growth detection checkbox in the Analysis Type pane.
    • Rerun the analysis.

    Also avoid running an interactive debugging session during analysis [200238394]

  • When using Intel Inspector with Linux desktop window managers on Linux OS like TWM and Ubuntu/Unity* window managers, there are known Linux window manager issues which may cause unexpected behavior (like disappearance of controls or even the whole GUI) or even spontaneous crashes of Intel Inspector.

    Recommendation: Switch to another window manager.


Memory Error Analysis Issues

  • Intel Inspector may report false positives when the analyzed application uses custom memory allocators. Use of _itt_notify to annotate your source code can reduce these false positives.
  • If the semantics of standard C runtime allocators are changed, the behavior of the Intel Inspector is unknown and could lead to abnormal analysis termination. For instance, if the application is using non-standard versions of these allocators where the memory returned by the allocator is initialized when it would normally be uninitialized.
  • Memory error analysis of applications that use Qt* APIs may report false positives.
  • On-demand leak detection will not report memory leaks until the end of the basic block in which they occur, as there is still an internal reference in the program to that memory. If the baseline for leak detection is not reset, these leaks will be reported at the next request [200348282]
  • Windows OS: If you turn on Analyze stack accesses for a memory analysis, then make sure the application being analyzed is not compiled with the default Microsoft Visual C++* setting /RTC1 or with /RTCs. These options cause a basic runtime check for stacks which uses a fill technique to detect uninitialized accesses that hides errors from the Intel Inspector's memory analysis.
  • Linux OS: The memory error analysis type with the narrowest scope may be slow for binaries that do not contain a binary search table in the .eh_frame_hdr section. [200154305]

Threading Error Analysis Issues

  • Intel Inspector does not detect deadlocks or potential deadlocks created with:
    • Some types of locks via Intel C/C++ parallel extension (__critical) provided by the Intel® Compiler Professional Edition 11.0 .
    • Some types of locks in Intel® Threading Building Blocks (Intel® TBB) (spin_mutex, spin_rw_mutex)
    • Non-exclusive ownership synchronization objects involved, for example, condition variables, semaphores and events and reader/writer locks.
  • Intel Inspector does not detect inter-process data races or deadlocks.
  • Intel Inspector may report false positives for analyzed applications using customized synchronization primitives. Use of _itt_notify to annotate your source code can reduce these false positives.
  • To enable correct analysis of Intel® TBB applications, set the following required macros before compiling:
    • TBB_USE_DEBUG (which sets TBB_USE_THREADING_TOOLS) if you use Intel® TBB debug libraries
    • TBB_USE_THREADING_TOOLS if you use Intel® TBB release libraries
  • Windows OS: Intel Inspector is not a replacement for a traditional debugger, such as the Visual Studio* debugger on Windows* operating systems or GNU gdb* debugger on Linux* operating systems. If an application crashes inside/outside the Intel Inspector, try running the application inside the debugger to reproduce and fix the crash.
  • Windows OS: Intel Inspector may report false positives when analyzing applications that use the Microsoft* Concurrency Runtime framework (Parallel Patterns Library, Asynchronous Agents Library, etc.).
  • Windows OS: Intel Inspector does not detect data races or deadlocks in system modules (say modules residing in Windows\System32 directory). For example, DX9 libraries and memory accessed by DX libraries installed in Windows system directory are not analyzed. To enable detection of the issues, move the modules to a non-system directory (say to the Windows* Program Files directory). [200139450]
  • Windows OS: Using multiple versions of the Microsoft .NET* framework in the same application may cause the Intel Inspector to hang.
  • On Linux, Intel Inspector does not capture the main thread creation site if the binary is built without debug symbol information.
  • On Windows, Intel Inspector does not capture the main thread creation site if :
    • The binary is built without debug symbol information.
    • The .pdb symbol file is not in the location specified within the .exe or .dll executable file or in the location containing the .exe or .dll executable file.
  • Linux OS: Intel Inspector is not a replacement for a traditional debugger, such as the Microsoft Visual Studio* debugger on Windows* operating systems or GNU gdb* debugger on Linux* operating systems. If an application crashes inside/outside the Intel Inspector, try running the application inside the debugger to reproduce and fix the crash.
  • Intel Inspector may report false positives if you have the Microsoft C runtime statically linked in the Windows application. On Linux, this issue may happen with libc or libpthread statically linked to the application. Recommendation: Build your application with Microsoft C runtime (on Windows) or libc or libpthread (on Linux) dynamically linked in.