- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After installing 11.1.060, when I set a breakpoint in other VS2008 projects that only have only C++ code, when debugging and the breakpoint gets hit Visual Studio crashes. Uninstall 11.1.060 and the crashes do not occur. It seems I can debug my FORTRAN projects without problems, but not C++ projects. Is this a known issue? It is very repeatable for me. I'm running on a 64 bit machine, running 64 bit apps. Vista Ultimate 64 is the OS. VS2008 SP1 installed.
Thanks,
Dave
Thanks,
Dave
Link Copied
50 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have been given the following suggestion:
- Open a command prompt as Administrator (right click on the shortcut for Command Prompt, under Accessories, and select Start as Administrator.)
- Change directory (cd) to Program Files\Intel\Compiler\11.0\066\fortran\uninstall
- Type the command: uninstall.exe c uninstall_cprof.ini -u
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try just renaming C:\Program Files\Microsoft Visual Studio 9.0\Common7\Packages\Debugger\ForDbgSW.dll to something else and see if that works instead of an uninstall.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried the uninstall command. It seemed to run okay, but I found that 11.0.066 was still listed as an application in Programs and Features, and it still had a listing under Start->All Programs->Intel...
And that I could still open the build environment cmd window. So I tried running it again. The second time I got the program has encountered an error window, and then the same message that the application was being uninstalled please wait message that I get running the uninstall from the Programs and Features menu.
And it is still there...
Dave
And that I could still open the build environment cmd window. So I tried running it again. The second time I got the program has encountered an error window, and then the same message that the application was being uninstalled please wait message that I get running the uninstall from the Programs and Features menu.
And it is still there...
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Maybe I should note again that I have a 64 bit machine so I keep changing your path names to be Program Files (x86) instead of just Program Files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, that would be correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Did you see that I tried your suggestion and it failed? It was in the post above the one you responded too.
Dave
Did you see that I tried your suggestion and it failed? It was in the post above the one you responded too.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, the uninstall failed. I will ask the developers again about this. Did you try renaming the DLL?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After installing 11.1.060 I renamed ForDbgSW.dll and tried to debug my AutoCAD plugin. It still fails when it hits a breakpoint in the code. What can you suggest we try to fix that now?
Dave
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please create a simple "hello world" C++ application and try to debug that - do you see the same error?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No it doesn't have the same error. Simple applications seem tohit breakpoints fine. But then it isn't capable of multiple threads either.It also isn't the same since I start up AutoCAD, which loads my .arx. Fortran programs don't give the same error either. But as soon as I uninstall 11.1.060 I can debug my .arx applications.
Dave
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have to wonder, then, if your .arx application is corrupting memory somehow. But why renaming the switcher DLL doesn't eliminate the problem is very odd, as that suggests that it isn't the Fortran debug support that is the issue.
I suppose the next test is to do a "modify" on Fortran and remove the VS integration, then try your test again.
I suppose the next test is to do a "modify" on Fortran and remove the VS integration, then try your test again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I installed 11.1.060 but unselected the integration into VS (kind of wierd that the next page of the installer forces you to pick which version to install into, and you can't go on without picking a version). Debug still fails. Uninstall and the failure ceases to happen.
Visual Studio only fails when it hits a breakpoint. If I don't have breakpoints it seems to run fine. It seems like a strange thing that I could corrupt memmory that only matters when the IVF compiler is installed. Not impossible, but seems very unlikely since we haven't had evidence of a memory overwrite in this application for years.
Stilling installing and uninstalling to keep working.
Dave
Visual Studio only fails when it hits a breakpoint. If I don't have breakpoints it seems to run fine. It seems like a strange thing that I could corrupt memmory that only matters when the IVF compiler is installed. Not impossible, but seems very unlikely since we haven't had evidence of a memory overwrite in this application for years.
Stilling installing and uninstalling to keep working.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
In addition to the above post I have tried the following. I uninstalled 11.1.060 and went back to 11.1.051. I have no problems debugging anything with 11.1.051 installed and integrated into VS2008. So it would appear something changed in 11.1.054 that has caused this issue. This problem started when I installed 11.1.060 directly from using 11.1.051. I had not tried 11.1.054 until after I couldn't use 11.1.060.
I also would still like to be able to uninstall 11.0.066. Does the check for another installer running come from Intel software, or from Windows Installer?
Dave
In addition to the above post I have tried the following. I uninstalled 11.1.060 and went back to 11.1.051. I have no problems debugging anything with 11.1.051 installed and integrated into VS2008. So it would appear something changed in 11.1.054 that has caused this issue. This problem started when I installed 11.1.060 directly from using 11.1.051. I had not tried 11.1.054 until after I couldn't use 11.1.060.
I also would still like to be able to uninstall 11.0.066. Does the check for another installer running come from Intel software, or from Windows Installer?
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok - that is getting interesting. If you remove just the Visual Studio integration and then delete the Intel Fortran folder under Visual Studio. does that change the behavior?
Next thing to try is to rename the Fortran LIB folder to LIBX and see if that makes a difference. I'm trying to identify what aspect of the compiler install is causing the problem.
Next thing to try is to rename the Fortran LIB folder to LIBX and see if that makes a difference. I'm trying to identify what aspect of the compiler install is causing the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Steve,
After removing the Intel Fortran folder I got the above message and VS crashes when hitting the breakpoint. I picked No to answer the form.
Just renaming the lib folder also resulted in a crash (after restoring the Intel Fortran folder).
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The install engineers suggest updating Windows Installer and then trying the uninstall again. I am rather doubtful that this will help, however.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok - that tells me that the integration did not actually uninstall. Restore the folder. Open a Fortran command prompt window as administrator (right click on the shortcut and select Start as Administrator). cd to that Intel Fortran folder and then to the VFPaclkages subfolder. Type the following commands:
regsvr32 /s /u VFHieEditor.dll
regsvr32 /s /u VFAVwin.dll
regsvr32 /s /u VFFortSvc.dll
regsvr32 /s /u VFProjConvert.dll
regsvr32 /s /u VFProj.dll
regsvr32 /s /u VFToolOpt.dll
Now try your C++ program.
regsvr32 /s /u VFHieEditor.dll
regsvr32 /s /u VFAVwin.dll
regsvr32 /s /u VFFortSvc.dll
regsvr32 /s /u VFProjConvert.dll
regsvr32 /s /u VFProj.dll
regsvr32 /s /u VFToolOpt.dll
Now try your C++ program.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It still has the same error after unregistering those dll's.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. First, I'd like you to right click on one of them, select Properties, Details and note the File Version. Do that for the rest of them - they should all have the same file version and should say 11.1.3470.2008. If they don't, delete that folder and reinstall 11.1.060, then do the regsvr32 commands again to unregister them.
After you have done that, again start a command prompt as administrator and CD to that folder. Now, one at a time, do:
regsvr32 /s VFToolOpt.dll
regsvr32 /s VFProj.dll
regsvr32 /s VFProjConvert.dll
regsvr32 /s VFFortSvc.dll
regsvr32 /s VFAVwin.dll
regsvr32 /s VFHieEditor.dll
Stop after each one and try your C++ program. When you get to the one that triggers the error, let me know. I have a theory that you may find that the error has gone away.
After you have done that, again start a command prompt as administrator and CD to that folder. Now, one at a time, do:
regsvr32 /s VFToolOpt.dll
regsvr32 /s VFProj.dll
regsvr32 /s VFProjConvert.dll
regsvr32 /s VFFortSvc.dll
regsvr32 /s VFAVwin.dll
regsvr32 /s VFHieEditor.dll
Stop after each one and try your C++ program. When you get to the one that triggers the error, let me know. I have a theory that you may find that the error has gone away.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
sorry I did that last test with 11.1.051 installed instead of 11.1.060. And 11.1.051 works fine. So went back and installed 11.1.060 and then unregistered those dlls. It still crashes VS.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, then. With the DLLs unregistered, open VS and select Help > About. Is Intel Fortran mentioned under Additional Products?
Still with the DLLs unregistered, rename the LIB folder. Does the C++ app still crash? Is this an EXE you run or that gets run somehow?
Still with the DLLs unregistered, rename the LIB folder. Does the C++ app still crash? Is this an EXE you run or that gets run somehow?

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page