Intel® Inspector XE

Check out the Parallel Universe e-publication

The Parallel Universe is a quarterly publication devoted to exploring inroads and innovations in the field of software development, from high performance computing to threading hybrid applications.

Issue #20 - Cover story: From Knights Corner to Knights Landing: Prepare for the Next Generation of Intel® Xeon Phi™ Technology, by James Reinders, Director of Parallel Programming Evangelism, Intel

Use maximum resources in Inspector XE

What does "Use maximum resources" option do on the data race detection analysis?

I found that there is a significant performance differcence between with and without that option. But the analysis results are not quite different.

For instance, for one program it took  about 15 seconds without the option while it took about 5 minutes with the option.

Does it make skip analysis for some parts of a program? Some kind of sampling technique?

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.

Intel® Parallel Studio XE 2016 Beta

  • Sviluppatori
  • Partner
  • Professori
  • Studenti
  • Apple OS X*
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • Client business
  • Server
  • .NET*
  • C#
  • C/C++
  • Fortran
  • Intel® Parallel Studio XE
  • Intel® Parallel Studio XE Cluster Edition
  • Intel® Parallel Studio XE Composer Edition
  • Intel® Parallel Studio XE Professional Edition
  • Intel® VTune™ Amplifier XE
  • Compilatore C++ Intel®
  • Intel® Inspector XE
  • Intel® Advisor XE
  • Compilatore Fortran Intel®
  • Intel® Cilk™ Plus
  • Intel® Trace Analyzer and Collector
  • Intel® Math Kernel Library
  • Benchmark Intel® MPI
  • Intel® MPI Library
  • Intel® Threading Building Blocks
  • Intel® Integrated Performance Primitives
  • Intel® Fortran Composer XE
  • Intel® Composer XE
  • Intel® C++ Composer XE
  • Intel® C++ Studio XE
  • Intel® Cluster Studio XE
  • Intel® Fortran Studio XE
  • Intel® Data Analytics Acceleration Library
  • Intel® Cluster Checker
  • Intel® Visual Fortran Composer XE
  • Kit di sviluppo del software Intel® Cilk Plus
  • Intel® Cluster Poisson Solver Library
  • Intel® Streaming SIMD Extensions
  • Message Passing Interface
  • Ricerca
  • Big data
  • Elaborazione basata su cluster
  • Debugging
  • Strumenti di sviluppo
  • Settore dei servizi finanziari
  • Geolocalizzazione
  • Sanità
  • Ottimizzazione
  • Elaborazione parallela
  • Threading
  • Vettorizzazione
  • 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?





    Iscriversi a Intel® Inspector XE