fortcom.exe creating c????? files in my TEMP directory, and not deleting them

[ferrad01]

My machine crashed overnight and it may have had something to do with my TEMP directory having 75,000 files called c???? where ???? is a set of 5 random digits. I rebooted and ran procmon to see who was creating them, and it is fortcom.exe. Any idea how I can suppress this or at least get it to delete them when it's finished with them?

[Steven_L_Intel1]

Please make sure you are running the current Update 10 of Fortran. We fixed a problem similar to this a couple of updates back, though the file names were different.

[ferrad01]

I'm running 11.1.065, not sure what update 10 is.

[Steven_L_Intel1]

Oh, very old version. Update 10 to Composer XE 2011.

Are you using /fpp?

[ferrad01]

No, not using /fpp

Well I'd never heard of Composer XE until now. I guess that's the new name for Intel Fortran from 12.0 onwards? We are reluctant to upgrade to v12 at this stage, would it help if I upgrade 11.1 to the latest release?

[Steven_L_Intel1]

Yes, Composer XE is the new name for the Intel Fortran compiler as of compiler version 12. I don't know if it would help to get the latest 11.1, but it can't hurt. Can you show me the contents of one of these C???? files?

[ferrad01]

I think I added cfiles.zip to this post however I can't see it. The Add Files dialog is not that user-friendly...

ah got it now

[Steven_L_Intel1]

Ok - are you using /Qipo? Please attach a buildlog.htm from the Debug or Release folder.

[ferrad01]

No not using /Qipo

Buildlog attached

[Steven_L_Intel1]

Here is what we have found. These files are created by the compiler to hold information in various phases, but are deleted when the compiler exits normally. Emphasis on "normally". You should not see these files persist unless the compiler is exiting with an internal compiler error or something similar. I see no evidence of that in the build log you sent. If you clear out your TEMP folder and simply compile one of the sources, do you get a Cnnnn file remaining after the compile finishes?

On my system, I see these only if the compiler gets an internal compiler error.

[ferrad01]

I don't see them when consciously looking for them, ie. when doing a good build, then looking. However I do a set of builds every night, and occasionally look in the TEMP dir. eg, I looked there now and saw:

05/17/2012 05:38 PM 0 c20042
05/17/2012 05:38 PM 0 c85282
05/17/2012 05:38 PM 0 c60042
05/17/2012 05:38 PM 0 c70882
05/17/2012 05:37 PM 0 c89562
05/17/2012 05:37 PM 0 c59402
05/17/2012 05:37 PM 0 c21162
05/17/2012 05:37 PM 0 c85802
05/17/2012 05:37 PM 0 c70762
05/17/2012 05:37 PM 0 c91082
05/17/2012 05:37 PM 0 c69202
05/17/2012 05:37 PM 0 c42482
05/17/2012 05:37 PM 0 c90962
05/17/2012 05:37 PM 0 c88522
05/17/2012 05:37 PM 0 c78002
05/17/2012 05:26 PM 371,032 c65002

I do interrupt the build process sometimes if I see it's failing, so maybe when interrupting the compiler it leaves these files lying around.

[TimP]

If you kill the compiler while it's running, there is no cleanup. It's preferable to have the compiler log into a temporary file which you can peek at while it's in progress to check for failure.