Intel® Inspector XE

Thread Error Analysis: Intel Inspector and boost::thread::once.hpp corrupts stack


I tried to use Intel Inspector (from XE 2015) with little success. The application I try to analyze uses boost threads and a boost spirit parser. Thread safety defines have been added (eg BOOST_SPIRIT_THREADSAFE).

The following example displays the problem. In normal Release/Debug builds the program will output :

$ build64/Debug/once_test.exe


If Intel Inspector XE 2015 is used with "Thread Error Analysis" the program fails with stack corruption during the execution of boost::call_once.

Inspector crashes when starting analysis with VS2012 debugger

I am working with Inspector XE2015 integrated with Visual Studio 2012.

Inspector has helped me to find uninitialized variable. I want to use debugger in the moment when this error occurs. However when I start Inspector in one of modes "Enable debugger when problem detected" or "Select analysis start location with debugger" all crashes: first the debugged program, then the inspector, and at last the Visual Studio.

What conditions did not I follow to have a success with this matter?

Severe (157): Program Exception - access violation

When I try to run any of the 3 analyses available in Inspector I get the error "Severe (157): Program Exception - access violation" and the line with the call of "omp_get_num_procs" is listed in the console output:

use omp_lib
integer*4 procs
procs = omp_get_num_procs ( )

I double checked that I use following settings in my project: /debug:full, /Od, /check:none, /libs:dll /threads /dbglibs (Debug Multithread DLLs), /Qopenmp.

The application has no response,when using the Intel Inspector XE collecting Result datata

Hi all,

       I find our application becomes very slow, then always has no response,when Use the Intel Inspector XE to coolect  the memory leaks or thread errors.

    Who met this kind of phenomenon?how I should  Set the something?





SSA not generating results file

I am trying to run the SSA (2013) on a project of ours  in VS 2010. When I build for static analysis the build completes but I do not get a results file. I do have some link warnings (see below):

1>message.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library
1>library.obj : warning LNK4221: This object file does not define any previously undefined public symbols, so it will not be used by any link operation that consumes this library

Installation Question

Hello all,

I have a general installation question about Intel® Inspector XE and and the other Intel software development products.  Once you've installed an update, is it okay to uninstall previous updates if they aren't uninstalled automatically?  For example, if I have "Intel Inspector XE 2015 Update 2" installed, will uninstalling "Intel Inspector XE 2015 Update 1" affect the functionality of the product?  And does the same go for the other Intel software development products such as Intel Composer XE? 

Thank you all in advance for your help,


Are these false positives?

I am running Inspector on a C++ application using OpenMP for parallel threading on Linux (Redhat 6).  In the "Locate Deadlocks and Data Races" tool, it reported a few correct data races, mostly on some counters that don't affect the output.  However, it also reported numerous data races under one ID in the Summary section that all appear to be in local stack variables allocated internally by the various threads.  They don't appear to be able to overlap in any way.  Is anyone aware of any issues with false positives similar to this?

Some of my Inspector settings were:

Cross stack access

Hi all,

I'm using OpenMP to parallelize a portion of my code, in a way that one subroutine is fine-grained parallelized, and other two subroutines are being called from the main program as a coarse grained parallelization.

Attached is an Intel Inspector screen shot which tells me that I do not have data race, but at least one of my threads access the stack of other thread, i.e., cross stack access.

How it can be resolved ?

Thank you,


Suscribirse a Intel® Inspector XE