Intel® Inspector XE

can't get tutorial to run properly

I have Inspector XE 2015, which I'd like to use to detect memory issues in my code.  I tried running the dynamic memory tutorial on win7 (64-bit), but I don't get the expected results.  Inspector doesn't report any issues in the code itself, only kernel issues.  I'll try attaching the project and results here.

Inspector XE Binary/Symbol files

Hi There,

I am currently trying to debug some code I have written using Inspector, and the errors I am getting are occurring within, along with some of the mkl pardiso functions.

Inspector however cannot give me source code level debugging as it cannot find the debug symbols for these source files/libraries. I have tried to give the directories to the libraries to Inspector but it has not helped.

How can I link the debug symbols for the intel mkl functions along with libiomp5?




Can binary/symbol and sources search paths use top-level and go recursive?

When setting up the Binary/Symbol search and sources searches, can I use a top-level dir and expect the tool to go recursive?


There are a boatload of subdirs in my project and I don't want to specify every dir



Inspector finds data races in libm functions (asin, acos, atan)


I have an openMP code that takes 8 instances of a class and uses them in parallel (the class itself is a well known particle physics simulation code). It runs slower on multiple cores than on a single core however.

When using Intel Inspector, I find data races in various functions of the class that seem to be related to basic maths functions in libm. See this screenshot for an example involving atan:

Application crash with memory profiler

Using Intel Inspector XE 2016, on Linux.  Profiling a large application that uses too much memory for valgrind, so unfortunately this is my final hope for locating a stack error.  Program is a 64-bit application, mixed-language, C and Fortran, Fortran compiled using ifort 15.0.2.  Analyzing using Memory Error Analyzer, with the overhead slider set to the middle (how do I turn off and on individual tests?).  "Error: An internal error has occurred. our apologies for this inconvenience.

how to inspect a dll (Autodesk Maya Plugin)

In my company, we are developing an Autodesk Maya Plugin. We are programming in C/C++, under Windows 7, using MS Visual Studio 2013. Our code compiles into a dll. This dll is then loaded into Maya (by us during testing, or by our customers). This is done using the standard approach to load plugins in Maya (one goes into a menu in Maya, and selects a dll to load). So, our plugin then executes from within Autodesk Maya.

Cross thread heap allocation/deallocation


We are using intel inspector XE 2016 on a game made on Unreal Engine 4 to find memory leaks. However it seems to report a lot of false-positive pairs of "missing allocation" and "memory leak". We suppose that all allocations in one thread but free'd in another thread are causing such false positive reports. Is there a solution/option to tell intel inspector that such reports are linked? We can't find our real memory leak as we are flooded in a lot of those reports.


omp data race condition detected


Intel Inspector has detected a data race condition that I cannot understand. The entire program has A SINGLE omp pragma:

#pragma omp parallel num_threads(m)
#pragma omp for private(n)
      for(n=0; n<m; ++n) {

Of course, "efunc" is supposed to be a thread-safe function and I'm using Inspector to verify this.

Version 2016 does not recognize Windows 10 as valid OS

I thought that with the release of Intel Parallel Studio XE 2016, there would be support for Windows 10.  On installation, the product integrates with both Microsoft Visual Studio 2013 and Microsoft Visual Studio 2015.  Regardless of version of Visual Studio, when I run Inspector I get errors about "operations system not supported." and I get a dialog about sending a crash dump to Intel.  Will someone on the Intel side please verify whether or not XE 2016 is supposed to work with Windows 10.  The product pages that I found at Intel's site indicate support for "Windows OS*" but are not speci

Подписаться на Intel® Inspector XE