Debugger is not showing variable contents

[Moonkyu_H_]

Hi,

My debugger is not showing most of the variable contents including some local variables, even do loop index.  The "Locals" window shows some local variables but not all.  Interestingly, it is not showing any integer variables.  I don't have any access to the module variables, either.

I've tried VS C++ 2010 SP1 Redistributable Package (X86) as recommended in the Intel Fortran 2015 release note, but it didn't help.  I had the issue with XE2015 but I am still having the same issue with my current setup of:

MS Visual Studio Premium 2013 : Version 12.0.21005.1 REL

Intel Parallel Studio XE2016 Composer Edition for Fortran Windows* Package ID: w_comp_lib_2016.0.110

Please help.

[Kevin_D_Intel]

Is all this happening under the Release or Debug build?

From your description it doesn't sounds like anything trivial with not setting appropriate debug related property settings.

Any chance of sharing your solution/project with us for us to try ourselves?

[Moonkyu_H_]

Every project involved was Debug build.  I understand it's hard to figure out the cause with the source code, but unfortunately I can't share the source code. 

[Kevin_D_Intel]

Ok, understood. I don’t know whether this will help shed any clues but maybe we could see how debugging behaves with something we both have.

The Parallel Studio XE 2016 includes many Fortran samples.  This may be too trivial of a test case, but we can try. Look under: C:\Program Files (x86)\IntelSWTools\samples_2016\en\compiler_f\psxe\NQueens.zip

Unzip and build the NQueens-Serial Debug configuration. To debug, set Properties > Debugging > Command Arguments to the value of 50. Set breaks at line 54 and 90 of nq-serial.f90, and start debugging.

At line 54, can you see variables and their values?
Continue to line 90, are you able to see variables/values?
Continue a few iterations, can you see the value of the loop variable ‘i’?

I’ll also ping my colleague who specializes in our debug solutions about his thoughts.

[Moonkyu_H_]

Hi Kevin,

I've tried your test case, and found the debugger was just working fine.  I was able to examine all the variables, both local and global.  

Perhaps, I am having trouble with my project has both C++ and Fortran codes but I am not really sure.

Moonkyu

[Kevin_D_Intel]

Ok, that is a helpful information.

Just to confirm my understanding, my reading of your initial post is that you were having problems with PSXE 2015 + VS 2013 even before you introduced PSXE 2016, is that correct?

When did this issue start?
Was it after a Visual Studio and/or Intel Fortran upgrade?

[Moonkyu_H_]

Yes, I had trouble with PSXE 2015 + VS 2013, and I am still having the same issue after installing PSXE 2016.  

I inherited rather large code package and ported to Windows VS/Intel Fortran system.  I am having the trouble ever since.