Debugging error (installation) in Intel 64 platform

[rasa]

I am getting the following error while trying to debug in a 64-bit machine. It has Intel Fortran 10.1.3948.2005 professional installed. There is no separate visual studio installation in the machine (either standard or professional version). I am using the premier partner edition of visual studio that comes with Intel Fortran. I was able to compile successfully. However, I am getting the error in debugging. I am debugging inside Visual Studio by setting a break point and stepping to it.

Unable to start program C:exe_name_path.exe

The components for the 64-bit debugger are not registered. Please repair your Visual Studio 2005 Remote Debugger installation via 'Add or Remove Programs' in Control Panel

I tried reinstalling the Intel compiler and I got the same error (again). This is my first try in an Intel 64 machine. Please let me know if I am missing any component or trick.

Thanks.

[Steven_L_Intel1]

This is a bug in the installer. We should have an update out sometime today (or maybe tomorrow) - 10.1.014 - which corrects this.

If you can't wait, the good news is that our install DOES place the remote debugger installation files on your system. You can find it at C:Program FilesIntelDownloadIntelFortranCompiler10installs emote debuggerx64 dbgsetup.exe. Run this - it will install the remote debugger and then run a configuration tool. It may prompt you about changing firewall rules, but you can ignore that. It is not actually going over the network. This will solve the problem of getting the error message when starting the program under the debugger.

[rasa]

Thanks Steve. I installed as per your instructions. But now I am getting a different error. I checked two programs and both of them gave the following error(s) after warning about the misalignment of common blocks (that's specific to my program).

Error44 fatal error LNK2023: bad DLL or entry point 'msobj80.dll'LINK
Error32 fatal error LNK2023: bad DLL or entry point 'msobj80.dll'LINK

Maybe I should wait for the official patch ?

[Steven_L_Intel1]

That's a different issue and is a Microsoft bug. The fix (in most cases) is to download and install Service Pack 1 for VS2005.