Installation of Fortran changes behaviour of Watch window

[Jozef1]

I've just installed Visual Studio 2008 on Windows 7 Ultimate 64-bit. Then I run a simple c-program in a debugger mode, stepped through the program and observed somevariables in a Watch Window. The watch Window behaved in a normal way, i.e., whenever the value ofa variable changed the color turned to red. However, after installation of the Fortran11.1.051 the behaviour changed. The value of a variable changes but the color remains black.

Does anyone know howto restore the proper bahaviour of the Watch window?

Jozef

[Steven_L_Intel1]

I had not seen a report of this previously, but I can reproduce it. I'll ask the developers what's up.

[Steven_L_Intel1]

Reported as issue DPD200141734. A workaround is to run the Update 3 (051) setup, select Modify, remove the VS Integration, then run the setup from Update 2 (048), and install the VS integration (you also need to have the Update 2 compiler installed, but you'll still be able to use the Update 3 compiler.)

[dajum]

Steve,

Is there then something being lost from the Update 3 VS integration package besides this new bug? What are the tradeoffs here to not using Update 3?

Dave

[Steven_L_Intel1]

You can refer to the List of Fixes - there are a couple of items there that are debugger-related. However, the tests I did suggested that it was not the actual debugger support that caused this change. One thing I have not yet tried is to install 11.1.048's integration but use the Fortran debugger DLLs from 051.

[Jozef1]

Quoting - Steve Lionel (Intel)

Reported as issue DPD200141734. A workaround is to run the Update 3 (051) setup, select Modify, remove the VS Integration, then run the setup from Update 2 (048), and install the VS integration (you also need to have the Update 2 compiler installed, but you'll still be able to use the Update 3 compiler.)

Unfortunately in my case it doesn't work. To make sure what is wrong I removed all Fortran versions and VS 2008. Then I installed VS 2008. As expected it worked fine, showing in red variables which changed their values. Then I installed the earliest version of Fortran I had on my computer, w_cprof_p_11.1.046_novsshell, and the problem came back. So, the problem is already in 11.1.046. And I think it is related to 64-bit OS since VS 2008 and ia-32 fortran 11.1.046 works fine on 32-bit Windows XP.

Jozef

[Jozef1]

Quoting - dajum

Steve,

Is there then something being lost from the Update 3 VS integration package besides this new bug? What are the tradeoffs here to not using Update 3?

Dave

The problem seems to be present already in version 11.1.046.
Jozef

[Steven_L_Intel1]

Jozef, why do you say that? My testing showed it not present in 046.

[Jozef1]

Quoting - Steve Lionel (Intel)

Jozef, why do you say that? My testing showed it not present in 046.

Steve,

I wonder if we are testing the same thing. I dida few more exercises, see #5 Reply to #2 (my reply to your 2nd reply), and I see the same problem with 046 as with 051. However, the problem is not present on a 32-bit Windows XP, where I installed only ia-32 046. I'll check what happens if I install ia-32 051 on that computer.

Jozef

[Steven_L_Intel1 · Accepted solution]

We have determined that the problem is caused by the new Parallel Debug Extension that was introduced in Update 2. You can disable this for now by moving or renaming VSDebugExtension.dll.

[Jozef1]

Quoting - Steve Lionel (Intel)

We have determined that the problem is caused by the new Parallel Debug Extension that was introduced in Update 2. You can disable this for now by moving or renaming VSDebugExtension.dll.

Thanks Steve. This time it worked.
Jozef