Intel® Inspector XE

Uninitialized memory access caused by IPP routines

Hello,

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.

Incorrect uninitialized partial memory access

I get a strange error with Inspector XE 2013.  The problem occurs when I try to access a derived data type that contains an int16 integer.  Intel Inspector says there is an uninitialized partial memory access error.  All variables are initialized.  The problem disappears if the integer type is changed to int32.  The attached code shows the problem.  My code was built with the latest Intel Fortran Composer XE 2013.  Any solutions?

using Inspector with third party software

   Hello

     I use Fortran third party software named Winteracter to build engineering app. My simple question is how can I run inspector outside Visual studio and inside Winteracter to perform Static security analysys in the code. My main concern is about uninitialized variables. Is there any compiler switch that I can add to make inspector avaiable during the building?

    Thanks in advance

                         Peter

SSA and preprocessor directives

I'm unsure about how the SSA works with the preprocessor directives, does it collects the SSA Information during the build process? And uses then the way through the directives, which is defined in the configuration/flags? Or does it ignore all of the directives? 

For example the following code:

constantVal = 6
#ifdef A
   tmpvar = 10
#else
   tmpvar = 0
#endif !A

tmpvar = tmpvar+1
tmpvar = tmpvar+1
tmpvar = tmpvar+1
tmpvar = tmpvar+1

#ifdef B
   tmpvar = tmpvar+1
#endif !B

many (wrong ?) error messages with inspector-xe

I try to use inspector-xe to find mistakes in a quite large Fortran/C software. But I get many memory mistakes which I don't understand. Most of the time : "memory leaks",  "Missing allocation" or "Invalid partial memory access". But I am unable to fix the problems.

For instance, in case of "Missing allocation", the explanation says that one tries to deallocate twice a same array or that a pointer is invalid. But in most of my programs, there is no DEALLOCATE statements because  ! use the automatic deallocation feature of F95 at the end of procedures.

Static analysis, inspxe-inject doesn't work (Fortran, on a linux box)

Hi,

i'm working on a hugh Fortan project which is build through several Makefiels, so the regular approach of the static analysis will not work for me. Also I'm working on a Linux maschine, thats why the VS-solution will not work as well.

So I tried to use the specfile-approach, but inspxe-inject doesn't work. The spec-file is created but the content is empty

the command:

inspxe-inject -save-spec spec1.spec -- make

creates a soec file, that looks like:

Performance problem

Hi,

I ran Inspector xe 2013 on Ubuntu 12.04.

I used two programs from PARSEC benchmark suite and it is so slow as the following shows

*****************************************************************

program   original time(sec)       Inspector time(sec)     slowdown  

facesim    5.99                              2634                             439

ferret        6.63                              2376                             358         

*****************************************************************

evaluation license

Hi,

i'm new to inspector but had a couple questions.

No matter what i do, when i start an inspection it says "Project is out of date  Project files or build settings were modified since the last build..."  I have cleaned and rebuilt the single project that is in my soolution.  i have even started a new project from scratch and moved all my source code only to run into the same message.  This didn't happen when i ran the tutorial.  Any idea why this is happening?

Intel® Inspector XE abonnieren