I've encountered a problem that appears to have arisen sometime in the last year with the debugger when trying to set a watchpoint on a Fortran variable:

Intel(R) Debugger for applications running on Intel(R) 64, Build [74.923.2]

(idb) whatis TESTVAR

type = COMPLEX(8) (64,800,6)

(idb) watch TESTVAR(36,326,1)

Watchpoint 2: TESTVAR(36, 326, 1)

However, with the newer version, I am unable to set a watchpoint:

Intel(R) Debugger for applications running on Intel(R) 64, Build [79.936.23]

(idb) whatis TESTVAR

type = COMPLEX(8)

(idb) watch TESTVAR(36,326,1)

could not insert watchpoint because its size is not supported as requested

Watchpoint remains disabled. It can be enabled later once the error condition is resolved.

(idb)

Note the improper size being reported with the "whatis" statement.  In both instances, I am debugging the same executable (which was built using compiler version 12.0.4), so it definitely appears to be debugger-related.

Thanks in advance.

Dear friends,

I am trying to find a way to debug Abaqus user subroutines but, since I am using Abaqus 6.13/VS2010/Intel12, I am not able to do it, as most of the instructions online are oriented to older versions.

I change the abaqus_v6.env file to link it with my compiler the way that is recommended in many places (http://yhtian.wordpress.com/2010/11/03/debug-abaqus-subroutine-with-visu...) but the debugger is not able to find the PDB file (vc100.pdb).

I suppose that one way to overcome this problem is to create the obj and PDB files first, but when I try to do it with VS2010 the way I do it with my fortran codes a compilation error appears and no PDB or OBJ files are created. This is quite normal since what I am trying to debug/compile by "brute force" is a subroutine that has no sense without the main code, but I have seen online some people that made it this way.

Any advice? Thanks a lot for your help

Emilio Mtnez

Dear all,

When debugging a FORTRAN program step by step, if the debugger gets into the execution of a statement expanding more than one line, the "step" command is stuck between the lines of the multi-line statement about ~18 cycles before it exits and continues to the next statement. For instance assume the following FORTRAN code that expands into two lines:

Line 1: ep_data(order(i))%EE = (ep_data(order(i))%landings + m_consumed(order(i))) & 
Line 2:             / (ep_data(order(i))%PoB * ep_data(order(i))%biomass)

Line 3: group_no = count(detritus_group_no(:) < order(i)) + 1

When the debugger gets into the execution of the first line (Line 1) of the statement, you can "step" to the next part of the statement on the second line (Line 2). Once you are on the second line, if you issue "step" one more time, the debugger prompt goes back to the previous line (Line 1). The debugger is held stuck between these two lines for about ~18 cycles until it breaks the cycle and proceeds to the following statement on Line 3.

I would be glad if you have an idea about this strange problem and could share the solution with me.

Best regards,

E.

I have IDB v13.0 running on Linux. When debugging  correct OpenMP threaded programs, the program being debugged always  hangs under IDB. That is, the program appears to have stopped running, and I have to break into IDB to see where it is stuck. Always the same place...

_ZN34_INTERNAL_12_src_pdbx_cpp_67bc0b7b4pdbx2io17log_communicationEv ()        libpdbx.so.5    0x00002B30D48AEB75
_ZN4pdbx6pdbx_t9configureEv ()        libpdbx.so.5    0x00002B30D48A824E
_ZN4pdbx6pdbx_t11synchronizeERKNS_6syncidE9mem_orderPKv ()        libpdbx.so.5    0x00002B30D48ACD8F
__itt_sync_acquired ()        libpdbx.so.5    0x00002B30D48BC4EC
_Z18__kmp_fork_barrierii ()        libiomp5.so    0x00002B30D23014A3
__kmp_internal_fork ()        libiomp5.so    0x00002B30D2300047
__kmp_fork_call ()        libiomp5.so    0x00002B30D22FC6A1

If I set OMP_NUM_THREADS=1, IDB functions as expected and the running program runs to completion.

which version of Intel System Studio support TNETC4830 Puma5 chipset? Any manuals, directions for JTAG Debugging of TNETC4830 Puma5? (JTAG debugger for Windows)

Hi,

I just installed Visual Studio 2012 and Intel Visual FORTRAN Compiler XE 13 on my 64 bit windows 7 computer. My problem is that in the debug mode the program algorithm works fine except it does not show the values of the variables. Following are some information about the problem:

1. I tried the watch window and also moving mouse over the variable but neither of them works.

2. I tried very simple codes like Hello World and just defined an integer but the program is unable to show the value of the variable in debug mode. 

3.This problem only happens in FORTRAN codes. In my C++ codes the debug mode works fine and shows all the variables values!

4.By default the Enable Native Edit and Continue option in Tools is off. If I turn this on the watch window shows the value of some of the variables but still I can not see the variables inside a vector for example and if I move mouse over a variable it does not show the value of it.

5.I looked into other posts like :In Debug mode Watch doesn't display proper values, but I could not find any solution to my problem.

Thanks for your help in advance. 

I was using bldk in simics Atom E6xx virtual system.and I using "gBS->SetVariable" in the bldk,and it successed,

but when I run simics again, I can not get the variable ,and I use "dmpstore" in shell to see the variable,it show it can not be found !

it also happen in the X57+ICH10 platform .  what is the problem?  whether the bios flash can not be written in simics?

if not,how to solve the problem?

wish your answer!

hi !

I dont know if i am posing on correcty forum.

sorry for it.

I have a pc with crosshair extreme iv and i suffer with blue screen. The blue screen showed a problem in e1q62x64.sys. I seached for driver but i dont know what files i need. Someone can post a link that i can download a correctly archive to solve my problem ? 

OS             : x86_64 GNU/Linux (CentOS 6.4)

Compiler   : Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 13.1.1.163 Build 20130313

Debugger  : Version 13.0

FFLAGS      : -debug -cpp -zero -convert big_endian  -traceback -fpe0 -g -debug extended  -assume byterecl -i4 -132 -fp-stack-check  -complex-limited-range  -check bounds,pointers,uninit -ftrapuv

Hi,

I have numerous cases when a routine is called with an array with explicit declaration of the array size, but the called routine reports different size. Here is an example:

subroutine get_c4(c4,num_px,sol)
    implicit none
    type(tet_t),intent(in) :: c4
    integer,intent(in)           :: num_px
    double complex,intent(in)    :: e_sol(num_px)
    ...

get_c4 is called with num_px=8585 and with a double coplex x(1:8585), but get_c4 reports 340:

(*** from inside get_c4 ***)

(idb) p num_px
$49 = 8585

(idb) whatis e_sol
type = COMPLEX(16) (340)

Is it a bug? Do I miss something?

Thanks in advance,
--Ted

For some time, in the release notes of the Intel Fortran Composer 2013, it is indicated that the Intel Debugger will be deprecated and using GDB is advised. However, compared to Intel Debugger, GDB is far inferior. For example, it cannot access allocatable arrays in a debugging session (please see bug http://sourceware.org/bugzilla/show_bug.cgi?id=9395). And this is a bug open since 2007 without a fix but an ugly workaround. For one using a lot of allocatable variables in his code, debugging my Fortran program with GDB is like a nightmare for me. Does Intel have any plans to help fixing bugs of GDB that impedes its usability almost totally?

Thank you.

I think I've encountered a bug in the 'idb session save' command of idbc on Linux, but I'd like to get confirmation from users in other environments before declaring it as such.

I specified session_file with an absolute path, but idbc reports it tried to create the default $sessiondir. While this is not the intended behavior, at least the handling was graceful. If I try to do the same at a breakpoint in my program, it throws an error with stack trace due to an unexpected condition.

I have been able to work around the absolute path issue by setting $sessiondir to my preferred destination, but at present (in my environment) the documentation and idbc executable are not in sync.

Terminal example: (important lines in bold)

login2$ idbc diagonalize_8
Intel(R) Debugger for applications running on Intel(R) 64, Version 13.0, Build [79.936.23]
------------------
object file name: diagonalize_8
Reading symbols from /home1/02146/jblair42/bin/diagonalize_8...done.
(idb) break 371
Breakpoint 1.1 at 0x407b74: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 372.
Breakpoint 1.2 at 0x40800d: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 372.
(idb) break 403
Breakpoint 2 at 0x4080ed: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 404.
(idb) break 405
Breakpoint 3 at 0x408116: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 406.
(idb) break 423
Breakpoint 4.1 at 0x408955: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 424.
Breakpoint 4.2 at 0x409162: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 424.
(idb) break 435
Breakpoint 5.1 at 0x408cc0: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 436.
Breakpoint 5.2 at 0x408cde: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 436.
Breakpoint 5.3 at 0x408d0d: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 436.
Breakpoint 5.4 at 0x408d17: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 436.
Breakpoint 5.5 at 0x408d2d: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 436.
Breakpoint 5.6 at 0x408ecf: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 436.
Breakpoint 5.7 at 0x408f81: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 436.
Breakpoint 5.8 at 0x408fad: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 436.
(idb) break 452
Breakpoint 6 at 0x409176: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 454.
(idb) break 438
Breakpoint 7.1 at 0x408d72: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 438.
Breakpoint 7.2 at 0x408fd2: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 438.
Breakpoint 7.3 at 0x408fe3: file /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90, line 438.
(idb) idb session save /home1/02146/jblair42/bin/idb_customizations.cmd
Cannot create session directory '/home1/02146/jblair42.idb/sessions/'.
(idb) run
Starting program: /home1/02146/jblair42/bin/diagonalize_8
[New Thread 22288 (LWP 22288)]
 Time to load hamiltonian into memory:  4.1000000E-03
 Chunk:
           0
          43
 Size of Chunk:           2

Breakpoint 1.1, diagonalize () at /home1/02146/jblair42/src/diagonalize_parallel_csr_sym.f90:372
372      allocate(prodPart(dim_hamiltonian), stat=ierr2)
(idb) idb session save /home1/02146/jblair42/bin/idb_customizations.cmd
Assertion failed: "!savedSessionSaveState" ./src/ui/cmds/cmdsession.C:300
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(_ZN15IDBAssertFailed3runEPKcS1_j+0xe) [0x61220e]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(_ZN14DTLU_namespace12assertFailedEPKcS1_j+0x1e) [0xb671ce]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(_ZN14CmdSessionSave5do_itER19CmdExecutionContextRN10BaseForCmd9CmdResultE+0xe5) [0xa17507]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(_ZN10BaseForCmd7executeEb+0xfc5) [0x65e419]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb() [0x60fbf8]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(_Z15ProcessCommandsv+0x54) [0x60ff08]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(__gxx_personality_v0+0x41d) [0x60dd25]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(_Z7idbMainiPPKcS1_+0x180) [0x60dfb6]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(main+0x3a) [0x60dcca]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x38cc81ecdd]
/opt/apps/intel/13/composer_xe_2013.2.146/bin/intel64/iidb(__gxx_personality_v0+0x232) [0x60db3a]

Linux info:
login2$ uname -a
Linux login2.stampede.tacc.utexas.edu 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed Aug 28 17:19:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I've tested this with several different programs. The behavior does not seem to be related to the program being run within idbc. Could someone else please test the 'idb session save' behavior and comment?

Thanks for your help

Hello,

Since my update to Visual Studio 2012 with Intet Fortran 2013, I no longer have acces to all my modules variables in the display windows while debubbing under idb.

I managed to create a small program which leads to the same bug (at the end of my post). If I execute it in debug mode, let's say with a break point at the "write" line, I can check the values of arrays X and Z but no Y (error : "Undefined variable Y"). I think it's beacuse "X" is used in the main program to define variable "TOTO" and "Z" because the compiler "sees" it in the "IMPLICIT REAL*8(A-H,O-Z)" during compiling.

I know it worked under VS2008 with Intel Fortran 2011 (my previous VS version), and I wondered if something has changed or if I made mistakes ?

Thank you so much in advance for your answers.

Best regards,

Mathieu

PS : the code exemple (and the log file in .docx format).

    MODULE MONMOD 

    IMPLICIT REAL*8(A-H,O-Z)
    ALLOCATABLE :: X(:),Y(:),Z(:)
    
    END MODULE MONMOD
    
    
    SUBROUTINE ALLOC
    USE MONMOD

    ALLOCATE (X(100),Y(100),Z(100))
    X = 1.d0
    Y = 2.d0
    Z = 3.d0
      
    END
    
    program TestMod
    use monmod
    IMPLICIT REAL*8(A-H,O-Z)
    
    CALL ALLOC

    TOTO = X(1)
    
    WRITE(*,*) TOTO

    end program TestMod

Dear Fortran experts, As a sub problem in my code I need to evaluate the following expression: lim 1 x -> 0+ ------------------ sqrt(-1) + 1/x The expression above is well defined in the extended complex plane. 1/x ---> Inf as x ---> 0. sqrt(-1) + Inf = Inf. 1/Inf = 0. To try it out I wrote a code, compiled and ran it with three different Fortran 95 processors and got two different results. REAL X COMPLEX I PARAMETER(I=(0.0,1.0)) INTRINSIC SIGN X=SIGN(0.0,+1.0) PRINT*,'X=',X PRINT*,'1/X=',1/X PRINT*,'I+1/X=',I+1/X PRINT*,'1/(I+1/X)=',1/(I+1/X) X=SIGN(0.0,-1.0) PRINT*,'X=',X PRINT*,'1/X=',1/X PRINT*,'I+1/X=',I+1/X PRINT*,'1/(I+1/X)=',1/(I+1/X) END In GFortran and Open64 (I+1/X) evaluates to (0.0,1.0) + (+Inf,0.0) = (+Inf,1.0) (assuming X=+0.0) which [probably?] should be interpreted as a the complex infinity. Intel Fortran I got (NaN,0.0) as result. Is this a bug in Intel Fortran or is there something here which I am not thinking of? Am I violating a Fortran rule or IEEE arithmetic rule somewhere? Dr. Fortran (Steve Lionel) kindly pointed it out to me that IEEE 754 does not define complex arithmetic. I assume then that Fortran has at least *some* rules about how complex arithmetic on the *extended* complex plane should be executed by the processor? Keywords: Fortran 95, IEEE 754, complex, extended real, extended complex, arithmetic, reciprocal.

Hi,

I have a problem with idb. It works as expected when run as root, but when run as normal user i get this error message, after a crash, upon loading the executable, and sometimes even before that.

The error message is:

#############################

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f4ad376f1ae, pid=30033, tid=139960566785792
#
# JRE version: OpenJDK Runtime Environment (7.0_45-b31) (build 1.7.0_45-b31)
# Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libgtk-x11-2.0.so.0+0x2481ae]  gtk_widget_set_tooltip_text+0x1e
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/davide/svn-repo/fluidSOS/rotatingCouetteModel/soton-solver-mixed-fd-spectral-method/hs_err_pid30033.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
#
/opt/intel/composer_xe_2013_sp1.1.106/bin/intel64/idb: line 75: 30033 Aborted                 (core dumped) java -jar $INSTALLDIR/debugger/gui/intel64/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -showsplash -gui -native $TTY $IDB_ARGUMENTS
There were problems starting IDB.
This usually indicates Java Runtime or library compatibility issues.
Please check your environment.
For details check the log file at /home/davide/.idb_13.0_linux_intel64_app/workspace/.metadata/.log.

######################################

The log file indicated contains:

######################################

!SESSION 2014-01-10 12:01:02.544 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_45
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
Framework arguments:  -gui -native -tty /dev/tty
Command-line arguments:  -gui -native -tty /dev/tty

!ENTRY org.eclipse.equinox.registry 2 0 2014-01-10 12:01:03.247
!MESSAGE The extensions and extension-points from the bundle "com.intel.debugger.ui.nl1" are ignored. The bundle is not marked as singleton.

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.269
!MESSAGE NLS unused message: ActionManager_deleteBreakpointAll in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.272
!MESSAGE NLS unused message: ActionManager_deleteBreakpointAllDesc in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.272
!MESSAGE NLS unused message: ActionManager_suspendDesc in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.272
!MESSAGE NLS unused message: ActionManager_interruptDesc in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.273
!MESSAGE NLS unused message: ActionManager_openPagingWindow in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.273
!MESSAGE NLS unused message: ActionManager_openSvenTriggerWindow in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.273
!MESSAGE NLS unused message: ActionManager_SearchSourceFile in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS unused message: ActionManager_suspend in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS unused message: ActionManager_interrupt in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS unused message: ActionManager_openAddressTranslationDialog in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS missing message: ActionManager_kill in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.274
!MESSAGE NLS missing message: ActionManager_killDesc in: com.intel.debugger.ui.messages

!ENTRY org.eclipse.osgi 2 1 2014-01-10 12:01:04.275
!MESSAGE NLS missing message: ActionManager_loadBatchFile in: com.intel.debugger.ui.messages

######################################

As I said i can use the debugger by launching it as root but it is just a workaround.

Any help appreciated.

Regards,

Davide

I've encountered a problem that appears to have arisen sometime in the last year with the debugger when trying to set a watchpoint on a Fortran variable:

Intel(R) Debugger for applications running on Intel(R) 64, Build [74.923.2]

(idb) whatis TESTVAR

type = COMPLEX(8) (64,800,6)

(idb) watch TESTVAR(36,326,1)

Watchpoint 2: TESTVAR(36, 326, 1)

However, with the newer version, I am unable to set a watchpoint:

Intel(R) Debugger for applications running on Intel(R) 64, Build [79.936.23]

(idb) whatis TESTVAR

type = COMPLEX(8)

(idb) watch TESTVAR(36,326,1)

could not insert watchpoint because its size is not supported as requested

Watchpoint remains disabled. It can be enabled later once the error condition is resolved.

(idb)

Note the improper size being reported with the "whatis" statement.  In both instances, I am debugging the same executable (which was built using compiler version 12.0.4), so it definitely appears to be debugger-related.

Thanks in advance.

Dear friends,

I am trying to find a way to debug Abaqus user subroutines but, since I am using Abaqus 6.13/VS2010/Intel12, I am not able to do it, as most of the instructions online are oriented to older versions.

I change the abaqus_v6.env file to link it with my compiler the way that is recommended in many places (http://yhtian.wordpress.com/2010/11/03/debug-abaqus-subroutine-with-visu...) but the debugger is not able to find the PDB file (vc100.pdb).

I suppose that one way to overcome this problem is to create the obj and PDB files first, but when I try to do it with VS2010 the way I do it with my fortran codes a compilation error appears and no PDB or OBJ files are created. This is quite normal since what I am trying to debug/compile by "brute force" is a subroutine that has no sense without the main code, but I have seen online some people that made it this way.

Any advice? Thanks a lot for your help

Emilio Mtnez

Dear all,

When debugging a FORTRAN program step by step, if the debugger gets into the execution of a statement expanding more than one line, the "step" command is stuck between the lines of the multi-line statement about ~18 cycles before it exits and continues to the next statement. For instance assume the following FORTRAN code that expands into two lines:

Line 1: ep_data(order(i))%EE = (ep_data(order(i))%landings + m_consumed(order(i))) & 
Line 2:             / (ep_data(order(i))%PoB * ep_data(order(i))%biomass)

Line 3: group_no = count(detritus_group_no(:) < order(i)) + 1

When the debugger gets into the execution of the first line (Line 1) of the statement, you can "step" to the next part of the statement on the second line (Line 2). Once you are on the second line, if you issue "step" one more time, the debugger prompt goes back to the previous line (Line 1). The debugger is held stuck between these two lines for about ~18 cycles until it breaks the cycle and proceeds to the following statement on Line 3.

I would be glad if you have an idea about this strange problem and could share the solution with me.

Best regards,

E.

I have IDB v13.0 running on Linux. When debugging  correct OpenMP threaded programs, the program being debugged always  hangs under IDB. That is, the program appears to have stopped running, and I have to break into IDB to see where it is stuck. Always the same place...

_ZN34_INTERNAL_12_src_pdbx_cpp_67bc0b7b4pdbx2io17log_communicationEv ()        libpdbx.so.5    0x00002B30D48AEB75
_ZN4pdbx6pdbx_t9configureEv ()        libpdbx.so.5    0x00002B30D48A824E
_ZN4pdbx6pdbx_t11synchronizeERKNS_6syncidE9mem_orderPKv ()        libpdbx.so.5    0x00002B30D48ACD8F
__itt_sync_acquired ()        libpdbx.so.5    0x00002B30D48BC4EC
_Z18__kmp_fork_barrierii ()        libiomp5.so    0x00002B30D23014A3
__kmp_internal_fork ()        libiomp5.so    0x00002B30D2300047
__kmp_fork_call ()        libiomp5.so    0x00002B30D22FC6A1

If I set OMP_NUM_THREADS=1, IDB functions as expected and the running program runs to completion.

which version of Intel System Studio support TNETC4830 Puma5 chipset? Any manuals, directions for JTAG Debugging of TNETC4830 Puma5? (JTAG debugger for Windows)

Hi,

I just installed Visual Studio 2012 and Intel Visual FORTRAN Compiler XE 13 on my 64 bit windows 7 computer. My problem is that in the debug mode the program algorithm works fine except it does not show the values of the variables. Following are some information about the problem:

1. I tried the watch window and also moving mouse over the variable but neither of them works.

2. I tried very simple codes like Hello World and just defined an integer but the program is unable to show the value of the variable in debug mode. 

3.This problem only happens in FORTRAN codes. In my C++ codes the debug mode works fine and shows all the variables values!

4.By default the Enable Native Edit and Continue option in Tools is off. If I turn this on the watch window shows the value of some of the variables but still I can not see the variables inside a vector for example and if I move mouse over a variable it does not show the value of it.

5.I looked into other posts like :In Debug mode Watch doesn't display proper values, but I could not find any solution to my problem.

Thanks for your help in advance.