Intel® Inspector XE

aassertion failure

Too bad, don't have installed a mailing client so I am posting the error here::

[Process]
Process Name: devenv.exe
Virtual Memory Size: 1222880K
Working Set Size: 515408K

[Assertion]
CrashedPID: 7324
CrashedTID: 9196
Expression: ("signal_t::_insert: this connection is already exists.", false)
File: C:\bb\INNLchep2w6r\b\b\tmpwjs2dl\sdks\release_win32-x86\gen_helpers_2.18.4\include\gen_helpers2\core\config/../functor/signal.h
Line: 260

Intel® Parallel Studio XE 2015 Update 3 Professional Edition for Fortran Linux*

Intel® Parallel Studio XE 2015 Update 3 Professional Edition for Fortran parallel software development suite combines Intel's Fortran compiler; performance and parallel libraries; error checking, code robustness, and performance profiling tools into a single suite offering.  This new product release includes:

  • Sviluppatori
  • Linux*
  • Fortran
  • Intel® Composer XE
  • Compilatore Fortran Intel®
  • Intel® Fortran Composer XE
  • Intel® Math Kernel Library
  • Intel® Fortran Studio XE
  • Intel® Parallel Studio XE Composer Edition
  • Intel® Parallel Studio XE Professional Edition
  • Intel® Advisor XE
  • Intel® VTune™ Amplifier XE
  • Intel® Inspector XE
  • 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

    Iscriversi a Intel® Inspector XE