I know this is difficult to believe, but Inspector XE 2016 (build 423441) reports only a maximum of 4 GB on its Collection Log tab.

I'm trying to debug a program that will use over 200 GB, and I'm looking at the Memory Used by Analysis Tool and Target Application.  The Current memory usage started over at 0 after the program hit 4 GB, as did the graph.

For instance, right now, 'top' shows 4748m for the virtual memory size, and Inspector shows 652 MB.  (652 + 4096 = 4748)

Inspector must be using unsigned int for the number of bytes, at least for reporting here.  Doh!

Unfortunately I can't use inspector for any of the projects that I am working on. I am not sure if it is related to a Windows update, as it used to work before, but now for any project, level 2 (Detect Memory Problems) and level 3 (Locate Memory Problems) of Inspector fail to work. I use Windows 7 Professional, SP1, If needed I can provide a list of installed updates.

I am using Inspector_XE_2016_update2 integrated with MSVS2010. I also tried Inspector 2017 beta with MSVS2012 and got the same error. Here is a part of log in Collector Messages in Inspector 2016:

...

Loaded module: C:\Windows\system32\sfc.dll, address range [0x0x6e9f0000-0x0x6e9f2fff]
Loaded module: C:\Windows\system32\sfc_os.DLL, address range [0x0x7fef5440000-0x0x7fef544ffff]
Loaded module: C:\Windows\system32\USERENV.dll, address range [0x0x7fefc020000-0x0x7fefc03dfff]
Loaded module: C:\Windows\system32\profapi.dll, address range [0x0x7fefbea0000-0x0x7fefbeaefff]
Loaded module: C:\Windows\system32\dwmapi.dll, address range [0x0x7fef9240000-0x0x7fef9257fff]
Loaded module: C:\Windows\system32\MPR.dll, address range [0x0x7fef54b0000-0x0x7fef54c7fff]
Loaded module: C:\Windows\system32\UxTheme.dll, address range [0x0x7fef96a0000-0x0x7fef96f5fff]
Loaded module: C:\Windows\system32\MFC100ENU.DLL, address range [0x0x608c0000-0x0x608ccfff]
Error: An internal error has occurred. Our apologies for this inconvenience. Please gather a description of the steps leading up to the problem and contact the Intel customer support team.
Application exit code: -1

This is a part of log messages in Inspector 2017 beta:

...

Loaded module: C:\Windows\SYSTEM32\sechost.dll, address range [0x0x7fefc790000-0x0x7fefc7aefff]
Loaded module: C:\Windows\system32\OLEAUT32.dll, address range [0x0x7fefded0000-0x0x7fefdfa6fff], minimal analysis
Loaded module: C:\Windows\system32\MSVCP100D.dll, address range [0x0x19860000-0x0x1995bfff]
Loaded module: C:\Windows\system32\VERSION.dll, address range [0x0x7fefb0a0000-0x0x7fefb0abfff]
Loaded module: C:\Windows\system32\VCOMP100D.DLL, address range [0x0x722f0000-0x0x7230bfff]
Loaded module: C:\Windows\system32\UxTheme.dll, address range [0x0x7fef96a0000-0x0x7fef96f5fff]
Loaded module: C:\Windows\system32\dwmapi.dll, address range [0x0x7fef9240000-0x0x7fef9257fff]
Loaded module: C:\Windows\system32\MFC100ENU.DLL, address range [0x0x5cc50000-0x0x5cc5cfff]
Error: An internal error has occurred. Our apologies for this inconvenience. Please gather a description of the steps leading up to the problem and contact the Intel customer support team.
Application exit code: -1

Both of them seem to crash when hitting MFC100ENU.DLL. No matter what build I use, 32 or 64, debug or release, Inspector keeps crashing before starting the project. Please let me know if there is any fix for it.

Thanks,

Dear Developer,

We would like to invite you to participate in the Intel® Parallel Studio XE 2017 Beta program. In this beta test, you will have early access to Intel® Parallel Studio XE 2017 products and the opportunity to provide feedback to help make our products better. 

Registration is easy through the following link. Please complete the pre-beta survey, register, and download the beta software:

Intel® Parallel Studio XE 2017 Pre-Beta survey

This suite of products brings together exciting new technologies along with improvements to Intel’s existing software development tools

New features in Intel® Inspector 2017

1.Support for 2nd generation Intel® Xeon Phi (code named Knights Landing)

2.Variable name detection for threading analysis (global, static and stack variables). In previous Intel® Inspector versions we reported line number but in 2017 Beta we give the variable name containing the diagnostic.

For more details and information about this beta program, check out the Intel® Parallel Studio XE 2017 Beta page, which includes additional information in the FAQ and What’s New documents.

Regards

I have noted the following in my code and was wondering whether it is a bug or working as intended.

I have some code that is within a single parallel region.

SB(i)=SIN(BETA(i))

Now SB is a module variable that is threadprivate on creation.

Beta is a variable that is shared, but has intent(in) into the subroutine where this is happening.

Yet I consistently get read/write dataraces on this line according to intel inspector. 

Does anyone know why exactly I get this read/write data race here? and what I can do to remove it?

Consider this simple program:

#include <string>
#include <assert.h>

void foo(const std::string& str)
{
   assert(str[0] != 0);
}

int main()
{
   foo("Test longer than 32 characters like this");
   return 0;
}

If the string passed to foo() is longer than 32 characters, then the assert throws an error. Detailed inspection shows first 16 characters of 'str' to be filled with 0 (therefore the string is - unexpectedly - altered)! Any workarounds?

Ray

InspectorXE 2016 - Update 2
Visual Studio 2015 Community

Hi, I'm trying to find memory leaks with Intel Inspector XE 2016, inside Visual Studio. I'm selecting "Select analysis start location with debugger", it says "Cannot initiate a Microsoft Visual Studio Debugger session". Then it starts my exe, but after hours, nothing has happened. No sign of output anywhere. How can I know what's going on?

I have just installed Intel Parallel Studio XE (parallel_studio_xe_2016_update3.tgz) to try out Intel Inspector XE. My platform is Ubuntu 14.04, 64-bit. I started it on my application and then it just crashed on me with this message:

Error: An internal error has occurred. Our apologies for this inconvenience. Please gather a description of the steps leading up to the problem and contact the Intel customer support team.
Application exit code: 255 

Can someone help me to figure out what's wrong?

Thanks!

--Laci

Hello everyone,

I have Intel parallel studio xe 2016 w/ upgrade 3. it is fully integrated w my Visual Studio 2015 Community Edition and I am on Windows 10. Whenever I use any of the tools I get an error message saying unsupported OS. I am pretty sure w/ the advent of update one that parallel studio is supposed to work on Windows 10. Any help would be great!

Hi,

I've recently started using Inspector XE 2015 Update 2.

Since installing it, whenever I run some of my developments through VS2013 I'm encountering a BSOD on sepdrv3_15.sys (with code 0xc0000005).
This happens even if I'm not preforming an inspection and just running the specific project.

Any ideas?

Thanks,

Jake

Hi

with intel inspector I noticed that a very small code like this

#include <iostream>
void test(int l)
{
    char * s = new char[l];
    delete[] s;
}

int main(int argc, char *argv[])
{
    test(512);
    return 0
}

triggers a mismatched allocation/deallocation for the variable s;

This only occurs after stl headers are included (like the iostream here in this example)

Is it a bug of intel inspector ?

For background information, I'm using Visual Studio 2015, intel compiler 16 update 3, and Inspector XE 2016 Update 3 (in Parallel Studio).

Thanks for your feedbacks.

Hello,

I have a C# console application that interfaces to a C++ codebase using a wrapper created by SWIG.

 I ran it through Inspector (on a Win7 64bit machine if it matters) and it did not detect any memory leaks even though I intentionally inserted a memory leak for validating the process.

After playing around with the settings for a long time, I realized that I should be using the "Mixed" Microsoft Runtime Environment. The next run of Inspector detected the leak... but none of of the subsequent run detect the leak! and I've tried everything I could think of! 

I've deleted all the results, recreated the executable, tried a different executable with the leak, switched to Auto and then back to Mixed... restarted the machine :)

Am I missing something obvious?

Please let me know if you'd like any other details to help me solve this mystery

thanks,

Julian.

as our ( large ) application starts up, I'm seeing data races reported that don't make a lot of sense to me. We haven't created ( our code anyways ) any threads yet. Is it possible these are false positives? Or is the false positive rate very low, and I should try to make sense of what I'm seeing? Once the app is running I see no data races ( so far ).

Hi all,

I use following Software:

* Microsoft Windows 
* Intel® Parallel Studio XE Composer Edition for C++ Windows* 2016
* Intel Inspector Xe 2016

Following codes cause Uninitialized memory access

std::all_of((uint8_t*)vector_type.data(),

                           (uint8_t*)(vector_type.data() + vector_type.size()),

                           [](uint8_t a) { return 0 == a; })

and

std::vector<uint8_t>(&var_name[2],

                            &var_name[var_name.size() - 60])

var_name.size if bigger than 100.

Can anyone explain me the reason of this error, pls?

I am trying to profile my project for memory errors with Inspector. When I start inspector it says that can't start debug session and will continue without debugger support. Also, I have this errors when I build project:

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.DAAL.v110.targets(37,5): warning : Could not expand DAALProductDir variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.DAAL.v110.targets(38,5): warning : Could not expand DAALMajorVersion variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.DAAL.v110.targets(39,5): warning : Could not expand DAALMinorVersion variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.DAAL.v110.targets(40,5): warning : Could not expand DAALIncludeDir variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.DAAL.v110.targets(41,5): warning : Could not expand DAALLibDir variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.MKL.v110.targets(38,5): warning : Could not expand MKLMajorVersion variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.MKL.v110.targets(39,5): warning : Could not expand MKLMinorVersion variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.MKL.v110.targets(40,5): warning : Could not expand MKLIncludeDir variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.MKL.v110.targets(41,5): warning : Could not expand MKLLibDir variable. The registry information may be incorrect.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v110\Platforms\Win32\PlatformToolsets\v110\ImportAfter\Intel.Libs.MKL.v110.targets(42,5): warning : Could not expand OmpLibDir variable. The registry information may be incorrect.

Actually, I had to fix MSBuild script by adding MKLProductDir and changing target platform from ia-32 to ia32 (before that I was getting another error about mkl_link_tool.exe can't be found/run

I am using Visual Studio 2012 and 2013, tried on both with the same result. Windows 8.1 with all latest updates for Windows and VS

Thanks,

Leo

Hi,

i wrote a simple OpenMP code. In this code i use MKL VSL Library to generate Random Numbers. If I run it outside Intel Inspector i don't receive any error. If i run it under Intel Inspector making Threading error analysis (-ti3) i don't receive any errors, but i run it under Inspector making a Memory Error Analysis i receive an error and a warning also if i receive an exit code equal to 0. 

This is the error:

P1: Error: Uninitialized partial memory access: New
 P1.50: Error: Uninitialized partial memory access: New
  /home/pierpaolo/PIC/NIS/Hybrid/DOUBLEINT/PROVA/Prova3.F(46): Error X50: Read: Function prova: Module /home/pierpaolo/PIC/NIS/Hybrid/DOUBLEINT/PROVA/Prova
  Code snippet:
   44        file=200
   45        filename='prova.res'>46        OPEN(file,FILE=filename,STATUS='REPLACE')
   47
   48        DO i=1,npmax,1000

  Stack (1 of 1 instance(s))
  >libifcore.so.5!for__open_proc - /opt/intel/composer_xe_2015.2.164/compiler/lib/intel64/libifcore.so.5:0xd6d21
   libifcore.so.5!for_open - /opt/intel/composer_xe_2015.2.164/compiler/lib/intel64/libifcore.so.5:0x5b5be
   Prova!prova - /home/pierpaolo/PIC/NIS/Hybrid/DOUBLEINT/PROVA/Prova3.F:46
   Prova!main - /home/pierpaolo/PIC/NIS/Hybrid/DOUBLEINT/PROVA/Prova:0x12f9
   libc.so.6!__libc_start_main - /usr/src/debug/glibc-2.12-2-gc4ccff1/csu/libc-start.c:226
   Prova!_start - /home/pierpaolo/PIC/NIS/Hybrid/DOUBLEINT/PROVA/Prova:0x1204

Also if i receive it my file is opened correctly.

And this is the warning:

P2: Warning: Memory not deallocated: New
 P2.195: Warning: Memory not deallocated: 31104 Bytes: New
  /home/pierpaolo/PIC/NIS/Hybrid/DOUBLEINT/PROVA/MyRand4.F90(51): Warning X195: Allocation site: Function myrand_mp_initrand2_$omp$parallel@46: Module /home/pierpaolo/PIC/NIS/Hybrid/DOUBLEINT/PROVA/Prova
  Code snippet:
   49          TID=idp*nthreads+OMP_GET_THREAD_NUM()
   50          brng=brng0+TID  ! TID.ge.0>51          status=vslNewStream(stream,brng,TID)
   52          WRITE(100+OMP_GET_THREAD_NUM(),*)status
   53  !$OMP END CRITICAL

  Stack (1 of 1 instance(s))
  >libmkl_core.so!mkl_serv_allocate - /opt/intel/composer_xe_2015.2.164/mkl/lib/intel64/libmkl_core.so:0xe1013
   libmkl_vml_avx.so!__vslAllocateStream - /opt/intel/composer_xe_2015.2.164/mkl/lib/intel64/libmkl_vml_avx.so:0x30611e
   libmkl_vml_avx.so!__vslNewStreamEx - /opt/intel/composer_xe_2015.2.164/mkl/lib/intel64/libmkl_vml_avx.so:0x3060a7
   Prova!myrand_mp_initrand2_$omp$parallel@46 - /home/pierpaolo/PIC/NIS/Hybrid/DOUBLEINT/PROVA/MyRand4.F90:51
   libiomp5.so!__kmp_invoke_microtask - /opt/intel/composer_xe_2015.2.164/compiler/lib/intel64/libiomp5.so:0x9fbb1
   libiomp5.so!__kmp_invoke_task_func - /nfs/fx/proj/openmp/promo/20141201/tmp/lin_32e-rtl_5_nor_dyn.rel.40.r1.c0.s0-fxeolin15/../../src/kmp_runtime.c:7060
   libiomp5.so!__kmp_launch_thread - /nfs/fx/proj/openmp/promo/20141201/tmp/lin_32e-rtl_5_nor_dyn.rel.40.r1.c0.s0-fxeolin15/../../src/kmp_runtime.c:5616
   libiomp5.so!__kmp_launch_worker - /nfs/fx/proj/openmp/promo/20141201/tmp/lin_32e-rtl_5_nor_dyn.rel.40.r1.c0.s0-fxeolin15/../../src/z_Linux_util.c:772
   libpthread.so.0!start_thread - /usr/src/debug/glibc-2.12-2-gc4ccff1/nptl/pthread_create.c:301
   libc.so.6!clone - /usr/src/debug////////glibc-2.12-2-gc4ccff1/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:115

In this last case i receive it also if a successfully use (status=vslDeleteStream(stream) ) receiving status=0 for each thread.

Any suggestions on how to solve these two errors?

Thanks in advance

Pierpaolo

Hi,
which is the directory in which Inspector runs the debugging session?
When I try to run Inspector with "Select analysis start location with debugger" it doesn't find some dlls that are in the same folder of the executable I'm trying to debug. (That are normally found when I debug normally).
I'm running Inspector from VS2015.

Hi, I'm having some troubles with the attached code SendReceive.c.

The idea is to open a dataset with process p-1 and then to distribute it to the remaining processes. This solution works when the variable ln (local number of elements) is less than 8182. When I increase the number of elements I've the following error:

mpiexec -np 2 ./sendreceive 16366
Process 0 is receiving 8183 elements from process 1
Process 1 is sending 8183 elements to process 0
Fatal error in MPI_Recv: Other MPI error, error stack:
MPI_Recv(224)...................: MPI_Recv(buf=0x2000590, count=8183, MPI_DOUBLE, src=1, tag=MPI_ANY_TAG, MPI_COMM_WORLD, status=0x1) failed
PMPIDI_CH3I_Progress(623).......: fail failed
pkt_RTS_handler(317)............: fail failed
do_cts(662).....................: fail failed
MPID_nem_lmt_dcp_start_recv(288): fail failed
dcp_recv(154)...................: Internal MPI error! cannot read from remote process

I'm using the student license of the intel implementation of mpi (obtained by installing Intel® Parallel Studio XE Cluster Edition (includes Fortran and C/C++)).

Is this a limitation of the licence? Otherwise, what I'm doing wrong?

Thank you for using Intel® software development tools. We are committed to making the best possible software and platforms to meet your development needs. Your personal experience with our products is extremely valuable to us and we want to know how we can do better.

Click here to share your thoughts by completing a 10-min survey on Intel® Parallel Studio XE, as well as your general tool usage.  We value your opinion and look forward to your feedback.  If you have any questions, post a comment below.

If you reside outside of the United States and decide to participate in this survey, you are agreeing to have your personal data transferred to and processed in the United States. Refer to Privacy for more details.

Hi,

Evaluating Intel Inspector 2017

I'm trying to locate deadlocks and race conditions in our game project, but analysis is running way too slow. I've include only one dll module (using Include only following modules option in project properties), stack frame depth 1, no suppression, project is compiled on release, /Zi, with optimalizations. It takes minutes just to load dll(s) and show splash screen and it would probably take hours to get to main menu and do actual analysis. 

How can i make it run faster? Can i attach to running process and instrument code later on.

Thanks

Andrew

VS 2015 Update 3, Intel Inspector XE 2016 Update 3 (build 460803), Windows 7 64 bit, analyzing a 64 bit program.

When I run the preset analysis "Locate memory problem" from the project node context menu, symbols for the program itself cannot be apparently loaded. When the program completes, a memory leak problem is reported in the Summary tab, but the lower pane says "Symbol information not found. Suggestion" etc. There is only the module name, and a hex address.

The program is built with debug information (I tried both /Zi and /ZI), and I can debug it just fine, the VS debugger loads symbols. Also, Inspector seems to report the location for another (probably bogus) problem of a mismatched allocation, pinpointing the location inside msvcp140d.dll all with source file and line number. It is only my own symbols that cannot be loaded.

How can I proceed troubleshooting from this point on?