Intel® Inspector XE

Intel(r) Parallel Studio XE 2015 Professional Edition

The latest release of Intel(r) Parallel Studio is now available.

If you have an active support license for Intel Parallel Studio, the Intel® Parallel Studio XE 2015 products are now available for download from the Intel® Registration Center.

New features for Intel® Inspector XE 2015:

Strange behavior in memory analysis

Hi all,

I have run a memory analysis (the widest scope memory analysis type) via Inpsector XE 2013. It includes analysing of stack acceses, to cach uninitialized arrays/variables.

Attached is a PNG figure with the results.

Note the strange behavior in Polar_HUCM.F90 module, which imply there is uninitialized memory access in line 119. However, note that line 120 is identical in terms of using the same arrays and specifically the same part of the array being controlled by "kb" loop.

Intel Inspector XE stack traces with C++ code

We are evluating Inspector XE 2015 and have version:
  Update 1 (build 379161)
When working with C++ compiled with the Visual Studio 2013 compiler inspector gives stack traces to memory or gdi leaks
with names like:

  libabc.dll!copy_or_grow
  libabc.dll!modify
  libabc.dll!abcString

whereas we would expect to see C++ class names included:

  libabc.dll!abcString::copy_or_grow
  libabc.dll!abcString::modify
  libabc.dll!abcString::utString

The Intel® Parallel Studio XE 2016 Beta program is now available!

Dear Developer,

The Intel® Parallel Studio XE 2016 Beta program is now available. In this beta test, you will have early access to Intel® Parallel Studio XE 2016 products and the opportunity to provide feedback to help make our products better.  Registration is easy through the Intel® Parallel Studio XE 2016 Pre-Beta Survey.

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

Cannot install evaluation of Intel Inspector XE 2015 on Linux without root acces

Hello,

Is it possible to install an evaluation of Intel Inspector XE 2015 on Linux without root access?  I usually just use it on Windows, and I'm just evaluating it on Linux, so I don't want to bother system administrators unless the evaluation proves successful.  Can someone please email me a license file?  As far as I can tell my purchased Windows license file won't work for a Linux install.

Missing Interactive Debugging "Debug This" Context Menu Item

Hello,

I'm trying to attach my debugger to see a data race in the act, but I can't find the context menu item "Debug This Problem" explained in the documentation "About Investigating Problems Using Interactive Debugging" ( https://software.intel.com/en-us/node/528095 ):

Inspector fails on most of OmpScr benchmarks

Hi,

I am running inspector on the OmpScr benchmark. The benchmark allow you to specify a problem size for each of the programs. When I run inspector using small size problem it is able to finish the verification process most of the time but for some of the problem (i.e. c_loopB.badSolution1.par). I get the error:

Error: Internal error. Please contact Intel customer support team.

Use maximum resources in Inspector XE

What does "Use maximum resources" option do on the data race detection analysis?

I found that there is a significant performance differcence between with and without that option. But the analysis results are not quite different.

For instance, for one program it took  about 15 seconds without the option while it took about 5 minutes with the option.

Does it make skip analysis for some parts of a program? Some kind of sampling technique?

Thread Error Analysis: Intel Inspector and boost::thread::once.hpp corrupts stack

Hi!

I tried to use Intel Inspector (from XE 2015) with little success. The application I try to analyze uses boost threads and a boost spirit parser. Thread safety defines have been added (eg BOOST_SPIRIT_THREADSAFE).

The following example displays the problem. In normal Release/Debug builds the program will output :

$ build64/Debug/once_test.exe
construct()
construct()

 

If Intel Inspector XE 2015 is used with "Thread Error Analysis" the program fails with stack corruption during the execution of boost::call_once.

Intel® Inspector XE abonnieren