debugger thinks I'm working in C

[ERIC_W_1]

I have just moved onto a new laptop. After reinstalling Microsoft Visual C++.net 2003 and reinstalling Intel Fortran (W_FC_P_9.1.024.exe) I find that the debugging Watch windows demand C syntax instead of the FORTRAN syntax that I was used to on my old notebook. For example, the FORTRAN syntax would be like PLEG%NUM_SEG. However, using this syntax produces CXX0017:Error: symbol "NUM_SEG" not found. But the syntax PLEG.NUM_SEG works fine. The problem also exists in the code window, so that hovering over a variable with a % in it does not work. So, apparently the debugger hasn't got the message to use FORTRAN syntax.

What have I forgotten to do to make this right?

[Steven_L_Intel1]

Sometimes this happens with VS.NET 2003 - the Fortran debug expression evaluator does not get properly installed. There is a way to fix it but I don't have the details handy and I'm away from the office. Please file an issue with Intel Premier Support and they can help you out.

Also, I would recommend downloading a more recent release, 9.1.033, though it won't affect this particular issue.

[ERIC_W_1]

Steve,

I passed this issue to Premier Support but they didn't have a solution. I suggested that they contact you but have heard nothing since. Would you please speak to them about it? I'm really stuck.

thanks,

- Eric

[Steven_L_Intel1]

Sigh - sorry to hear that. I'll get you the answer on Monday.

[Steven_L_Intel1]

Open the folder C:Program FilesMicrosoft Visual Studio .NET 2003Common7PackagesDebugger (this assumes a default installation - ifyou installed somewhere else modify the path appropriately.

First, select the following files and make a copy of them in the folder (right click, drag, copy)

NatDbgEE.dll
CppEE.dll
ForDbgSw,.dll

CppEE.dll may or may not be present.

Exit Visual Studio

Now, if CppEE.dll existed, delete it. Rename NatDbgEE.dll to be CppEE.dll

Rename ForDbgSW.dll to be NatDbgEE.dll

This should take care of the problem.

[ERIC_W_1]

Steve -

Worked like a charm.

Thank you SO much!

- Eric

[Steven_L_Intel1]

Wonderful - glad to hear it.

For the benefit of anyone else who runs across this thread, this solution applies to VS.NET 2003 ONLY!!!! Not 2002, not 2005. 2003! 2003 is the only one where this particular problem arises.If you think you have this symptom and aren't using VS.NET 2003, and reinstalling the VS integration doesn't fix the problem, do not try the steps listed here - contact Intel Premier Support instead.