I have Intel Fortran Composer XE 2013 running within Visual Studio 2012. I am trying to evaluate the Static Analysis function of the Fortran. It seems that it requires Intel Inspector XE. I have installed an evaluation copy of Inspector XE. The operation "Build project for Intel Static Analysis" completes without errors and tries to display the results in Inspector XE. The message "Invalid license for Static Analysis" is displayed by Inspector XE. What am I missing? Is some other component needed? The inpector tool can be started stand-alone and show a valid evaluation license.
I have been running my code successfully with my Intel Fortran 10, right now I need to add more allocatable variables and I got an error "insufficient virtual memory". I am sure my computer has enough memory to run this program. Is there a way to change the setting in fortran in some way to make this work? Thanks
This is a general topic, but I did not find any "Forum" specific search option. The only search box that shows up is for the entire intel.com site at the very-top. It seems that "search" should be just before "new-topic"!
Can code compiled with mingw-gcc on windows be analyzed using Inspector?
Does the intel debugger recozgnize gdb debugging symbols?
Does the code need to be compiled with specific debug switches (-ggdb, -g-dwarf2 etc.)?
I am using Intel Parallel Inspector 2011 on a Windows machine, along with the 11.1 compiler, and receive multiple warnings on stack cross access for my FORTRAN code, which I do not understand.
The FORTRAN code has multiple parallel regions, separated by serial sections. A subroutine REALLOCP is called (once during the execution) in a serial section, in which several global arrays are allocated. These arrays are used later in the progrm in parallel DO loops. The Inspector flagseachaccess to these arrays inallparallel sections with the Stack Cross Access warnings.
I am getting critical errors with weight 100 for allocating an array with zero size.
allocatable a(:) allocate(a(0)) end
we are evaluating Inspector XE and we have made a few successful test runs. However we get a lot of false positives regarding Qt.
Regarding to this site: http://software.intel.com/sites/products/documentation/doclib/stdxe/2013... the inspector should be able detect the Qt-APIs we are using. Although we are also using QMutexLocker, but since this is only a convenient wrapper for QMutex it should be fine.
I am getting an "Error 255" before Inspector seems to perform any memory analysis on my C program. I am doing a static compile with C and some Fortran mixed in (icc and ifort) but the same failure happens when I compile dynamically. The error I get is rather cryptic and I can't find the description of Error 255 in documentation. I'm quoting the log file below. Is there something wrong with my program's compile settings? Valgrind runs on it. Thanks!
<?xml version="1.0" encoding="UTF-8"?>
When investigating problem set, there are only five top stack elements shown for a problem. It is not always enough for my task. How to view more that five elements of stack for a problem?
I'm using Intel Inspector to check my C++ code which is using Intel IPP. I got strange errors "Uninitialized memory access" and "Uninitialized partial memory access" pointing to IPP functions. On the attached screenshot, an error is selected. Both allocation side and read points to the same line of my own source code - imageutils.cpp:23. I also attach the full report.
It seems like the error is caused by an IPP function. Is that true, or am I doing something wrong?
I'm using Intel Inspector XE 2013, Intel IPP 7.0.205, Windows 7 x64, Visual Studio 2010.