Intel® Inspector XE

No complaint about use of uninitialized variables in simple Fortran test cases?


I'm trying to use Inspector on the simple examples in the Polyhedron test suite (, but I don't get the error reports I expect.  Am I doing something wrong?

Taking UIN7 as an example, it's compiled from the command line using

ifort uin7.for      /debug:full /Od /libs:dll /threads /dbglibs



I am trying to run:

mpirun -np 2 inspxe-cl --result-dir insp_results -collect mi1 -- myApp

but i get the following error:

Fatal error: Cannot start collection because the Intel Inspector XE 2013 failed to create a result directory. Unknown error

This message comes only once, if I start 3 jobs 2 times, 4 jobs 3 times, etc.

inspector create only one directory insp_results, so without numbers.

What is going wrong?

best regards,


APIs for Custom Synchronization

While the Intel Inspector supports a significant portion of the Windows* OS and POSIX* APIs, it is often useful to define your own synchronization constructs. Any specially built constructs that you create are not normally tracked by the Intel Inspector; however, the Intel Inspector supports synchronization APIs to help you gather semantic information related to your custom synchronization constructs.

Subscribe to Intel® Inspector XE