Compiler Crash Out

Hello,

I get the following:

Some of the details dialogs:

This exception occurs from time to time when I attempt to build my project which consists of a FORTRAN DLL project and a number of .NET projects.

The wierd thing is that it occurs maybe 1 out of 20 times, on W7, on XP however it is a fair bit more common.

Thanks, Alex.

I think that you have provided enough information for me to be able to find the point at which FTN95 crashes (provided only that you are using the current FTN95 and the relevant file has not been changed in the mean time).

I should then be able to get FTN95 to provide a diagnostic report that will indicate why the failure is occurring and hence the construct within one of your modules that FTN95 is not handling correctly. Hopefully this will enable you to find a work-around.

This could all be short-circuited if you were able to provide short sample code that exhibits the crash but I guess this would not be feasible.

As far as I can tell the failure arises because the compiler is expecting that the name of a library file contains a back-slash. If I have the right point in the code then a search is starting from the end of the name of a library file and is going past the start of the name when a back-slash is not found.

In order to investigate further I really need some sample code to work on.

Quoted from PaulLaidler As far as I can tell the failure arises because the compiler is expecting that the name of a library file contains a back-slash. If I have the right point in the code then a search is starting from the end of the name of a library file and is going past the start of the name when a back-slash is not found.

In order to investigate further I really need some sample code to work on.

Hey,

Sorry for the late reply, time got away from me. The code base is quite large and I have no idea which part of the code is causing this error to happen.

What kind of code sample would you be interested in?

Thanks, Alex.

In order to find out where the program is failing, compile your code using /DEBUG or better /CHECKMATE. Then run the program using the debugger.

Ideally I need the code for a short working program that demonstrates the failure.

Quoted from PaulLaidler In order to find out where the program is failing, compile your code using /DEBUG or better /CHECKMATE. Then run the program using the debugger.

Ideally I need the code for a short working program that demonstrates the failure.

As stated this problem does not occur every single time we build the application and happens mostly either on Windows XP or on the CI server as a build job.

I am also not allowed to distribute the code base for the project, and not knowing where the issue is in the code base I cannot give you the whole thing or any of the input data that would be required for successful application run through.

I will try to narrow it down as I go, but I think it is the way the compiler is being executed using my build scripts rather then the code it is compiling.

Sorry, Alex.

My reading of the post is this appears to be a compiler bug, occurring at compile time. If you compile with the compiler messages going to a file, this might give a better idea where the problem is occurring. Other options that might help are: /BU /STAT

ftn95 program.f90 /bu /stat >compile.tce