Serious debugger problems in VS2010 Prof. & IVF 12.0.4.196

[joerg_kuthe]

Dear Fortran friends,

I recently got a new laptop (i7-2630QM running Win7 Ultimate, 64-bit) and also upgraded to VS2010 Prof., and installed IVF 12.0.4.196. Then I copied my VF projects to the new computer, converted these projects successfully, rebuilt completely and was ready to continue my programming work on this new machine.

Unfortunately I encountered some serious problems with the debugger (the regular debugger which comes with VS2010, not the Intel Paralled debugger ext.):

1. Values of local variables of a function or subroutine are not displayed correctly. For example, before the execution of

vP(:) = raFPunktXYZ( rGk(iFl), phiU(iFl), betaG(iFl), zEv(iFl), psi(iFl) )

I am checking all of the parameters and find them to be 0.0 (both the local variables window and the tooltip display 0.0).

Then stepping into the function, the debugger shows that most of the values of the arguments are NOT 0.0 (again, I checked the local variables window and the tooltip view).

Unfortunately I cannot supply screen shots. The problem occurs with a program I develop for a customer and I am not allowed to provide more information due to a nondisclosure agreement. I have tried to reproduce the problem with other Fortran projects but couldn't find a proper example (yet).


2. A minor problem, but annoying: Values of TYPE members are not shown anymore in the "tooltip view" (aka "bubble help"). The same is true for array elements. For example, in VS2005 I marked
ptRp % rDurchmesser(j)
or
rK(ind)
and pointing with the mouse arrow on this selected item caused a tooltip to display the member's or array element value, respectively. This isn't working anymore. So, to check a TYPE member's value, I have to scroll through all the components which can be quite tedious since several of my TYPE structures have dozens of members. This is even worse with huge arrays.

Does anyone has similar experiences? Or is this a problem just occuring on my machine?

I hope someone can help. Thank you.

Kind regards,

Jrg Kuthe
www.qtsoftware.de
www.qtsoftware.com

[joerg_kuthe]

I'd like to add an observation to the problem I described above. All of the local variables whose values are not displayed correctly in the debugger are declared using the SAVE attribute:

REAL(qt_K_DOUBLE), SAVE :: phiU(2), zEv(2), betaG(2), rGk(2), psi(2), rK

With the other local variables in the routine that are not SAVEd, I don't see this strange debugger behaviour. Their values can be tracked without problem.

Jrg Kuthe

[Steven_L_Intel1]

Without a test case, there's not much we can do for you.