IVF/VS2008 command line crash after successful build.

[jparry68]

I have a build script (ant) that kicks off 20+ projects for multiple languages to include C++, C, and FORTRAN. I have IVF version 11.1.060, VS2008 SP1 on a quad-core dell T7400 machine running XP SP3.

When I build each of the above projects using the MSIDE, no problems. But when I run command line, I get a crash after a sucessful build of a vfproj file. I did verify that the target built in the lib output directory and the log file also indicates success, but msdev still crashes on the command line only.

BTW, the above builds were executed using the DEBUG/WIN32 configuration. If I were to run against RELEASE/WIN32 configuration in command line, it does work.

As an additional data point, I do have another dev machine that is running VISTA 64bit (single CPU) with the above software and the build works perfectly on the command line using those projects and ant xml build script.

I have done the following:

- reinstalled everything

- run repairvs08integration.exe to correct reg entries

- set VSbuild max number of parallel project builds to 1

- disabled my virus checker

Anyway, if there is someone that has this problem or knows how to get around it, I will sing praise to you.

Thanks in advance,

John

[mecej4]

Here is one thing to try, if you have not already done so: have the IDE generate a makefile, attempt to build with make. If this works, try to locate the build step where the ant and make processes differ.

It seems to me that you have so many third party items in your build tools chain that it is unlikely that there is someone else in the same situation.

It is not clear to me why the problem is an Intel Fortran issue. Is the compiler or one of the associated tools failing? If so, how? "But when I run command line, I get a crash" is just not specific enough.

[Steven_L_Intel1]

Microsoft did away with the IDE-generated makefiles in VS2002.

[jparry68]

I originally thought this problem went away after I realized that having the IDE up that generates NCB files caused my crashes, but it was not the only one. It still continues to crash on other machines after a successful build (i.e the dll product was created with no errors in the build.htm file). When I look at the error report generated it says an access violation occurred in module vfproj.dll which leads me to believe it is an ivf problem.

I have tried re-installs, setting the number of parallel builds to 1, turning off the file scan option on our virus checker, altering output of the projects, but nothing has worked.Without any clue as to what this error is, I am stuck.

Anyway is there anyone that has experiences this problem using ivf(11.1.060)/vs2008SP1?

The interesting thing that I did not mention earlier is that we do builds out of clearcase and when I take the projects as is and copy them to my local c drive, they build perfectly everytime through the ant build script.

Thanks in advance.

[Steven_L_Intel1]

I have no experience with Clearcase, but if it plugs into VS, then the VF project system will indirectly call it and any errors you get will be attributed to vfproj.dll.

[jparry68]

I agree with you that Clearcase should work fine since I can build this in the IDE everytime without error, but Steve is there any meaningful info that I can get out the compiler through some debug setting to tell me what is going on? It smells like a timing problem since I can do a series of runs with some working and others failing without changing any of the projects.

Thanks in advance.

John

[Les_Neilson]

John,
Can you be a bit more explicit about what you mean by "crash"

For example we run a batch file which runs a series of other batch filescalling devenv to rebuildour system.
At the end of buildingcertain solutions a message box appears saying VS has encountered a problem and needs to restart. We always click the box "Dont restart VS" and "Don't send" (a report of the problem to MS)

The output of the solution (lib, dll etc) has always been created ok and the system carries on (to the next interuption).

This happens ontwo machines (our old "build" machine and it's soon-to-be replacement)but never on mine Building the problem solutions using the IDE works onboth build machines.

We have never been able to get to the bottom of the problem.

Les

[Steven_L_Intel1]

I know of no debugging information available.

[jparry68]

Les, what you are describing is exactly what is happening in our environment except in our ant script we have the failonerror element set to true so we abort as soon as we see that error. I am sure if I set to false, it will continue to the next crash and so on.

It saddens me that you have not been able to find a solution to this. We have pushed so hard to move away from CVF/VS6.0 unsupported but built fine to this which atm does not appear to be a step up from the build perspective.

Steve, if you are reading this... what steps does the ivf compiler do once the build has been completed? ie... removal of rsp and bat files, what else could I look at? Sorry to be such a pain, but desparation is quickly taking hold.

Thanks in advance.

John

[Steven_L_Intel1]

The compiler isn't doing anything at that point. You can look in the build log to see what operations are done, but I suspect it is some interaction between the project system and the source management system that is going awry. You can report it to Intel Premier Support and perhaps our IDE engineers will be able to look at it. Be sure to include everything they need to reproduce the problem, including where to get whatever third-party software you are using.

[jparry68]

It appears my problem was a bad SP1 install disk. I ended up discovering another one and installed followed by a reboot. 2 of the 3 machines are now working correctly in compiling the projects. The 3rd will be updated tomorrow morning. Anyway thanks for the help Steve, it looks like you were right...

John

[Les_Neilson]

John,
Interesting.
The SP issue wouldn't seem to apply to us as we have a central server where the software is kept and we install from there, so my machine and the two build machines will all have had the same SP file.

I forgot to mention: the build stops at different places on the two build machines(reproducability is a problem) and occasionally changes to a different project :-(
Last weekthere wasone day when the current build machine did not stop once, then it was back to normal stopping once or twice per build.
The replacement machine had been stopping several times per build- today it has only stopped once (so far).

Les