Visual Studio .NET Debugger not working with Intel Fortran

[akh123]

Hello all!

I've run into an itneresting issue. I've been trying to use the debugger that is part of the MS Visual C++ .NET 2003 Standard to debug Fortran code (Intel Fortran Compiler V8.0).

The trouble is, none of the variables I add to the watch list are ever recognized (they are reported as being undefined) I can view no arrays using the Array Visualizer, and the Command Window (in Immediate mode) doesn't understand any of the variables either.

What could be causing this? I read in the Forums here that the Intel Fortran compiler is completely supported by the VS.NET debugger.

Any help would be greatly appreciated.

-kirk

[Steven_L_Intel1]

Yes, it violates your license for IVF. Those files are not considered "redistributable".

[jbalster]

Is there any way to purchase a license for only the debugger component of IVF? We are currently working on a contract to convert our FORTRAN code to C++ 7 which requires Visual Studio .NET 2003. This is only for a temporary basis so we cannot justify the cost purchasing 9 more full copies of IVF just for the ability of using the debugger with no intention of ever using the FORTRAN 8.0 compilier. We would be willing to pay a modest amount for just that one component of IVF. Who would we contact at INTEL to address this possible license purchase????

[Steven_L_Intel1]

No, sorry, we don't sell it that way.

[jbalster]

Are the debugger support files included with the standard version of IVF or only with the professional version? Are they also included in the trial version?

[Steven_L_Intel1]

The Standard and Professional editions are identical except that the Professional also includes the IMSL Fortran libraries.

The trial version is identical to the Standard Edition. The debugger support is in all of these, but is subject to the license.

[Steven_L_Intel1]

This is a long thread - exactly which problem is it you are seeing?

The current compiler version is 8.1.023 (the version number you give is actually the IDE integration version, not the compiler version).I would recommend contacting Intel Premier Support if the issue, whatever it is, does not seem to be resolved in the current version.

[jbalster]

Dear grfeijo@sandia.gov ,

You only mentioned the C++ compilier. The problem this thread was addressing was not being able to see FORTRAN arrays in the debugger. For me, the fix was to have the following 4 files from the INTEL VISUAL FORTRAN (IVF)copiedonto each of mymachines.

C:Program FilesMicrosoft Visual Studio .NET 2003Common7PackagesDebugger

03/05/2004 03:49a 249,856 fordbgee.dll

03/05/2004 03:49a 53,248 fordbgsw.dll

03/05/2004 03:50a 589,824 forops.dll

03/05/2004 03:49a 53,248 NatDbgEE.dll

In my case, I am using the olderCVF 6.1 with Microsoft C++ that comes with Visual Studio .NET 2003. I had to purchase 10 copies of IVF to get the licenses to use the above mentioned 4 files. These debugger files work with either FORTRAN, CVF or IVF.

If your situation is different, you should contact Intel Premier Support.

[krojas]

I have experienced the same problem of examining variables in a .NET debugging session with IVF 8.1.025 (12/3/04). I've included a simple program that will demostrate the problem. This is the same example I've submitted to premier.intel.com as issue number: 275151.

I set breakpoints at each of the print statements during debugging to examine the program variables. The print statements in the code produce the correct output to the console (1 & 2 respectively). At the first print statement, I can navigate the watch tree down tdd(1).Tile_Drain_Practice.draincode but the value is not 1 as expected, but some long integer. Then at the Tile_Drain subroutine print statement, I try to watch tdd and get a "undefined variable tdd". Hope this helps.

My colleagues and I are very concerned about this deficiency with the intel compiler -- we don't see this behavior in the Salford 95 Compiler or with CVF running with VC6. We would like to recommend the Intel compiler for use by our Agency on a national basis because it's blazingly fast, but this is a serious concern for debugging purposes. Any help with this would greatly appreciated. We need to make a recommendation on which compiler to buy for our developers in the agency to national headquarters by the end of this week.

PROGRAM Data_Prep_Control
TYPE Tile_Drain_Practice
INTEGER::draincode
ENDTYPE Tile_Drain_Practice
TYPE(Tile_Drain_Practice),ALLOCATABLE,TARGET:: tdd(:)

ALLOCATE(tdd(1))
tdd(1)%draincode = 1
print*,tdd(1)%draincode
CALL Tile_Drain
CONTAINS
SUBROUTINE Tile_Drain
tdd(1)%draincode = 2
print*,tdd(1)%draincode
ENDSUBROUTINE Tile_Drain
ENDPROGRAM Data_Prep_Control

[krojas]

Steve-

The issue number for my post to premier is: 275151

thanks,
Ken

[Steven_L_Intel1]

Ken,

All I can tell you is that we have engineers investigating the problem. I am confident that it will get fixed, but I don't know when.

[evangelos_boutsianis]

Dear all,

allow me anxiously to ask for any new info on this same problem. I must add that this problem occurs ONLY when Visual Studio .NET 2003 is installed on a directory other than C:. I have followed the fix:CS-015862 and everything worked EXCEPT from the debugger. I have also noticed that the forops.dll, fordbgsw.dll and fordbgee.dll are MISSING from the folder ..Common7PackagesDebugger. The error message that I get when starting the debugger is: "The Fortran Debug expression evaluator is not properly installed..."

Please advise

Vangelis

[Steven_L_Intel1]

That problem is different and was fixed by the 8.1.021 update.

[borisk]

Has there been any progress on that issue lately ?

[williamrrichmond]

Hello:

I have just installed version 8.1.030 of the Intel Visual Fortran compiler and I am still running into similar problems with the MS NET debugger and Intel Visual Fortran. It appears to be able to drill further down into the subroutinesand be able to get the values of the variables, but when I go into a internal subroutine within a subroutineI lose access to all of the external variables.

Has anyone else had any similar problems?

Bill

P.S. For the Intel support with access to the problem board, please see issue number263998.

[Steven_L_Intel1]

We have fixed some bugs in 8.1.030, but more remain. If you find new problems, please report them - that way they'll get fixed. We do have engineering actively fixing the debugger bugs.

[krojas]

---

sblionel wrote:
We have fixed some bugs in 8.1.030, but more remain...

---

Steve- Does 8.1.030 address my simplest of example from ID#: 11746? We've been waiting for many moons for Intel to address this...

Thanks for keeping them moving on our behalf. I don't know how they sleep at night, knowing they are selling a product and collecting a paycheck, that is only 1/2 functional. Having a functional debugger is a Necessary part of a software development IDE.

[Steven_L_Intel1]

Ken, I think it does. There is a new 8.1.031 which should be available from Intel Premier Support now, I suggest you try that.

[Steven_L_Intel1]

Ken,

I just tried your example and it works perfectly in 8.1.030.

Message Edited by sblionel on 05-27-2005 04:48 PM