Visual Studio SP1 Crash on exit

[AndrewC]

I have a Visual Studio 2005 (SP1) solution with mainly C/C++ projects but one Fortran project ( I am using 9.1.034)
And I did uninstall all Intel products before upgrading to SP1

Everytime I exit Visual Studio I get a crash in Visual Studio, the stack trace points the finger at the VFTool integration.

Any ideas?

> VFToolOpt.dll!081cb7f9()
[Frames below may be incorrect and/or missing, no symbols loaded for VFToolOpt.dll]
VFToolOpt.dll!081cda89()
VFToolOpt.dll!081c1b61()
VFToolOpt.dll!081c1ab2()
msenv.dll!501ab856()
msenv.dll!501a84b9()
msenv.dll!501a5a36()
msenv.dll!501a59a4()
msenv.dll!501c90e4()
msenv.dll!500f336a()
msenv.dll!5006e90c()
msenv.dll!500cb027()
msenv.dll!506ee942()
msenv.dll!500cb027()
msenv.dll!50004dd9()
kernel32.dll!7d4e30c6()
kernel32.dll!7d505426()
msenv.dll!500f543a()
devenv.exe!0040a4a9()
devenv.exe!004068cf()

[Steven_L_Intel1]

I haven't seen this. Please create a ZIP of your solution folder and attach it to a problem report sent to Intel Premier Support. We'll be glad to take a look.

[AndrewC]

I've submitted a bug report. But the usual problem - our solution folder, zipped, is huge and proprietary.
Perhaps your support team could send a debug version of the DLL with PDB. Then we could isolate the exact location of the crash in your DLL. That often is a big clue to the problem.

[Steven_L_Intel1]

That's not helpful in this sort of a problem. However, the actual source files are probably not needed - just the .sln, .suo, .vfpoj and .vcproj files. It may well be that the Fortran support DLL is just "an innocent bystander".

[kent_myers]

We have exactly the same problem. We described it before.

http://softwarecommunity.intel.com/isn/Community/en-US/forums/post/30229931.aspx

No solution yet?

[Steven_L_Intel1]

Please give me the number of the Intel Premier Support problem report you submitted. I'm unable to find a matching report.

[AndrewC]

The only solution we found was to take the VF projects out of the solution (:
I was not able to give Premier Support a reproducible example

[kent_myers]

It only happens with one (main) solution. It has16 projects, one is Fortran, the rest are C++. Another thing, if you just choose "Close Solution" and then leave it for a while, then close, it may not crash.

[AndrewC]

Your setup is very similar to ours ( one FORTRAN project, multiple C++ projects). The bug was killing us as our automated builds kept failing with a studio crash. Breaking out the FORTRAN projects was the only solution in the end.

[jackosullivan]

VFtool might be the villain. Their current home page ( http://www.vftool.com/)shows that their 03/22/2007 Release 2.20 " Fix[es] a bug - if the .dsp file contains non-existing file, VFTool will on longer close DevStudio."

Do you users of VFtool consider it a worthwhile purchase?

Thanks and God bless!

Jack

[John4]

According to the home page's FAQ, VFtool is not supposed to work on any Visual Studio.NET version.

As was discussed in comp.lang.fortran a while ago, DVF/CVF already had most of the functionallity that VFTool was supposed to add ---so when people buy the VFtool add-in, they're essentially paying for the discovery of what they already have.

...And maybe that's why VFTool is not yet supported in the VS.NET versions ---i.e., IVF does not have source browsing/intellisense support yet.

John.

[Jugoslav_Dujic]

I think there's a misunderstanding going on here: the "VFtool" in the original post refers to standard Intel Visual Fortran integration component, residing in:

C:Program FilesMicrosoft Visual Studio 8Intel FortranVFPackagesVFToolOpt.dll

...and not to www.vftool.com, which is a 3rd-party program.

[Steven_L_Intel1]

We did find and fix a problem that sounds similar to this. Please let us know if the problem remains in version 10.0.

[jackosullivan]

Thanks very much, Jugoslav, for straightening me out ... and for all your terrific help in the forum.

Thanks, too, John, for the info on VFTool.

God bless!

Jack