Compiler diagnostics/debugging

[Dishaw__Jim]

I am compiling in a cygwin command shell since the project uses GNU makefiles for the build. The build proceeds normally until it reaches one of the source files at which point it appears to hang. The CPU and disk activity goes to zero. Sometimes I can abort the build by typing ^C. Other times the system is wedged to the point that I need to reboot. I cannot kill fortcom.exe via the Task Manager.

I specified the /watch:all flag to see if there is any indication where the problem may lie, but no luck. Is there are any other diagnostic flags that I can use?

The version of the compiler is 9.0.29. Incidentally, the entire project builds correctly with the Intel Linux Fortran compiler. I'm thinking this is a cygwin problem, but it is hard to tell without more diagnostic information from the compiler.

[Steven_L_Intel1]

It's not clear to me that the compiler could tell you anything useful. If you can't even kill fortcom.exe with the task manager, that suggests that something in the environment, perhaps the file system hooks Cygwin uses, are causing problems.

Can you compile this file ok NOT using Cygwin? Are the sources on the local PC or are they on a network share?

[Dishaw__Jim]

Well, it isn't a cygwin problem. I reproduced the bug using the "Build Environment for Fortran IA-32 applications" cmd window.

Here is the interesting point, the project exists on a network drive. If I go to the network share in windows explorer (after I started the build and it hangs), then windows explorer will hang. If I open another cmd window and attempt to go to that drive, the cmd will hang. The only way to resolve the problem is a reboot.

I copied the project over to the local hard drive the file compiles without an issue.

The problem appears to block all I/O on the network share, the question is whether it is a bug in the compiler or in Windows XP.

[Dishaw__Jim]

I noticed there is an 030 version of Fortran now, so I will download that and see if I have the same problem.

[Steven_L_Intel1]

I think you've already proved to yourself that it isn't a compiler problem. You have a network share access problem.

[Dishaw__Jim]

I agree that it is a network share problem, I'm just trying to figure out what the compiler is doing that causes the problem. The problem only occurs when I am in offline mode (the laptop is disconnected from the network).

I only experience this behaviour with the Intel Fortran compiler. The older CVF never caused this problem nor does gcc. I also don't experience this problem with other applications (Mathematica, Word, etc). There is something the Intel compiler does that triggers this behaviour in Windows XP.

Thanks for any help

[Steven_L_Intel1]

There's no diagnostic modes in the compiler that will help you here. The compiler makes standard C I/O calls to read the source files, though it may be doing fseek calls too.

Is it just the sources coming from the network share or are object and module files also going there? If so, you could experiment with having some of those go to a local disk. It would be interesting to see if the behavior changes as you change compiler options (try compiling with no switches, for example.)