Intel® Debugger

Why does the debugger (VS2013) keep hanging up ?

This is an issue with VS2013 shell, not VS2010.

We were required to go to this later shell to support newer releases of Fortran, like 17.0


after a debugging session. And then when I say "stop" or "restart" I get the "blue circle of death."

Meaning that it crashes after 30 seconds or so, and then I cant do another build, compile or anything else.

I get a message that says "debugger may be unstable." The only way to get back into my project is

Open Source Downloads

This article makes available third-party libraries, executables and sources that were used in the creation of Intel® Software Development Products or are required for operation of those. Intel provides this software pursuant to their applicable licenses. [Intel® Graphics Technology, Intel® Composer XE, Intel® C++ Composer XE, Intel® Application Debugger, Intel® Many Integrated Core Architecture Debugger & Intel® JTAG Debugger]
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • C/C++
  • Fortran
  • Intel® Parallel Studio XE Composer Edition
  • Intel® C++ Compiler
  • Intel® Fortran Compiler
  • Intel® Debugger
  • Intel® JTAG Debugger
  • Application Debugger
  • EPL
  • third-party
  • Debugging
  • Development Tools
  • Graphics
  • Intel® Many Integrated Core Architecture
  • Open Source
  • sample_decode erro~~help me~


          i use the sdk to decode h264. when i run the sample_decode whith the parameter "./sample_decode h264 -i test.264 -rgb4 -o out.rgb"

    will get an error when the program over, and i take an breakpoint to trace it. it occur in

    mfxstatus MFXVideoSession::Close(void) {

         mfxStatus mfxRes = MFXCLose(m_session):m_session = (mfxSession)0;

         return mfxRes;

      but ,if no paramets "-rgb4" this error will never occur, please help me ,thanks very much!

     system :Windows 10

    visual stdio 2012

    Debugger unable to display array contained in derived type


    I did post this some time ago on the Intel Visual Fortran forum, but I go no answer so far. I hope I will have more success on this forum.

    Since months debugging has been a hell because of a bug in the Intel Compiler and/or debugger integration: basically most (but not all) arrays are displayed with the length 0 in the debugger, and their content cannot be shown. The bug happens with allocatable arrays, pointers or static arrays. Of course it makes debugging pretty impossible, and I have to use WRITE statements... For instance the debugger shows me this:

    gdb woes

    Have Intel Parallel Studio XE Cluster Edition Version 16.0 update 3 installed on Cent O/S 7.2 and am having debugger issues (gdb-ia).

    Using Eclipse neon on KNL with PHOTRAN extension.

    The application is

    C main compiled using the Intel mpiicc (the C main is an MPI process stub)
    C++ code with OpenMP (num threads set to 1)
    Intel Fortran .so library which is being debugged

    gdb-ia version 7.8-16.0.768
    Note, on startup it emits

    warning: Cannot parse .gnu_debugdata section; LZMA support was disabled at compile time


    Subscribe to Intel® Debugger