Intel® Debugger

Intel® Visual Fortran Composer XE 2013 SP1 for Windows*, Update 5

Intel® Visual Fortran Composer XE 2013 SP1 Update 5 includes the latest Intel Fortran compilers and performance libraries for IA-32 and Intel® 64 architecture systems. This new product release now includes: Intel® Visual Fortran Compiler XE Version 14.0.5, Intel® Math Kernel Library (Intel® MKL) Version 11.1 Update 4, Intel® Debugger Extension 7.5-1.0 for Intel® Many Integrated Core Architecture (Intel® MIC Architecture)

New in this release:

  • Разработчики
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • Fortran
  • Intel® Fortran Compiler
  • Intel® Debugger
  • Библиотека Intel® Math Kernel Library
  • Редакция Intel® Parallel Studio XE Composer
  • Intel® Fortran Composer XE 2013 SP1 for Linux*, Update 5

    Intel® Fortran Composer XE 2013 SP1 Update 5 includes the latest Intel Fortran compilers and performance libraries for IA-32, Intel® 64, and Intel® Many Integrated Core (Intel® MIC) architecture systems. This new product release now includes: Intel® Fortran Compiler XE Version 14.0.5, Intel® Debugger Version 13.0.0, GNU* Project Debugger (GDB*) 7.5, Intel® Math Kernel Library (Intel® MKL) Version 11.1 Update 4

    New in this release:

  • Разработчики
  • Linux*
  • Fortran
  • Intel® Fortran Compiler
  • Intel® Debugger
  • Библиотека Intel® Math Kernel Library
  • Редакция Intel® Parallel Studio XE Composer
  • Fortran PARAMETERs shown twice in debugger

    When a Fortran program containing PARAMETER declarations is compiled with the /Zi /debug-parameters:used options, the parameters are displayed twice in the Locals window. Here is example code:

    ! test viewing PARAMETER values in debugger
    !
    program tst
    implicit none
    integer, parameter :: N=10,M=20,L=M+N
    integer :: iv(M-N),i
    !
    do i=1,size(iv)
       iv(i)=N+i
    end do
    write(*,*)iv
    end program
    

    I have attached a screenshot of the duplicated display of the parameters in the debugger.

    Signal Processing Usage for Intel® System Studio – Intel® MKL vs. Intel® IPP

    Employing performance libraries can be a great way to streamline and unify the computational execution flow for data intensive tasks, thus minimizing the risk of data stream timing issues and heisenbugs. Here we will describe the two libraries that can be used for signal processing within Intel® System Studio.

    Intel® Integrated Performance Primitives (Intel®IPP)

  • Разработчики
  • Linux*
  • Проект Yocto
  • C/C++
  • Начинающий
  • Средний
  • Intel® Parallel Studio XE
  • Intel® System Studio
  • Intel® Debugger
  • Intel® Integrated Performance Primitives
  • signal processing
  • Intel FFT
  • Intel DCT
  • FFT
  • Инструменты для разработки
  • Процессоры Intel® Atom™
  • Процессоры Intel® Core™
  • Оптимизация
  • Параллельные вычисления
  • Intel System Studio 2015 (Beta) Quark JTAG access to MSR

    Is it possible to gain access to the Quark's Model-Specific Registers (MSR) via JTAG using the XDB?

    If it is possible, in which way can I gain access to these registers?

    The Quark Debug Operations Manual suggests this [Direct quote form the Quark Debug Ops Manual, Section 5.6.11]:

    Intel Sytem Studio 2015 (beta), OpenOCD Quark Real Mode Debug

    Is it possible to debug the Quark SoC with Intel System Studio 2015 (Beta) and an OpenOCD probe? 

    The processor always stops at the address 0x0008:0xFFFFFA72 when following the steps state below. When the debugger halts the processor at address: 0x0008:FFFFFA72, the processor is already working in protected mode, so my technique of rewriting the EIP to go back to the address in memory pointed by the jmp instruction (see the steps below) at the reset vector is useless.

    Is there a way of debugging in real mode or stopping the processor before it enters protected mode?

    Подписаться на Intel® Debugger