Intel® Inspector XE

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

Hi

I'm trying to use Inspector on the simple examples in the Polyhedron test suite (http://www.polyhedron.com/wp-content/uploads/2014/04/win32_diagnose_src.zip), 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

Internal error, application exitcode -1

Greetings,

First of all, sorry for double-post, but it seems my post got lost after submitting.

I have application compiled with ICC 14.0 Update 4 (since ICC 15 has bug/internal error).

Both inspector XE 2013 and XE 2015 displays similar results in bot MSVC 2013 IDE and ran as a standalone application.

I have Haswell, Win 8.1 Pro x64, target app x64, 16 GiB RAM.

Here is copy-paste of log saying actually nothing except of "internal error". NB: sensitive informations, particulary full paths were obfuscated by upper-case "XXX" without quotes:

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

Hi

I'm trying to use Inspector on the simple examples in the Polyhedron test suite (http://www.polyhedron.com/wp-content/uploads/2014/04/win32_diagnose_src.zip), 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

MPI

Hi,

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,

Jaap

Subscribe to Intel® Inspector XE