Edit a value in the Watch window

[NBG6]

I'd like to edit a REAL*8 variable in the Watch window. But when I double-click the value column and try toentera value with floating-point(i.e. "4.7") I get the error message:

"The value could not be set. Please check your entry."

An integer-value without floating point can be entered.

What could be the reason?

Tanks!

Best regards,

NBG6

[Jeffrey_A_Intel]

A few details please, such as the version of Visual Studio and the ifort version. If you're using VS2005 or later, try the latest 11.1 ifort release. A bug was fixed in this area recently (but I don't recall exactly which update it was in).

[NBG6]

Sorry for the late response.

I have Visual Studio 2008 Version 9.0.21022.8 and the Intel Visual Fortran Compiler 11.1.3462.2008 .

[IDZ_A_Intel]

That's not the compiler version. What is the string that starts with w_cprof_ ?

[abhimodak]

Probably the following is not the case but I have seen this message if it is an array and I am trying to set a wrong index (for example, array A has lowe bound of 1 and I try A(m) = somevalue with m = 0). Note that the watch window would still display A(m) something but I believe that is whatever the "memory at that location" is pointing to (I don't know the correct wording).

Abhi

[NBG6]

Oops!

The compiler version is 11.1.035

[NBG6]

Abhi, thank you. But I think thats not the case. I have this problem with botharraysand scalar variables.

[gorbit]

I have got the same Problem also by editing REAL*4 values setting a value with a floating point.
The compiler version is w_fc_p_10.1.030 IA32 with Intel Debugger Version 10.1-35 running on VS 2008 Version 9.021022.8 Professional Edition. If it is a bug, has it already been fixed?

best regards

[IDZ_A_Intel · Accepted solution]

Using 11.1.060, I can't see any problem editing real scalars or arrays, single or double precision, in the debugger.

[NBG6]

My collegue has the same problem in editing real values using the compiler version 11.1.035. Recently he updated to 11.1.060 and now he has no problems any more. So I think the bug has been fixed in the new version.


Thank you very much for this hint!