Problem with IVF 11

[lklawrie]

I hate these problems.

I have a mixed project -- has some c libraries, modules, etc.

Both debug and release work fine inside the Visual Studio environment.

Outside, the debug version compile works fine. The release version does not.

All it gives me is a program exception - access violation. #157.

Ideas on what to try?

Linda

[ender01]

Quoting - linda@lawrie.com

I hate these problems.

I have a mixed project -- has some c libraries, modules, etc.

Both debug and release work fine inside the Visual Studio environment.

Outside, the debug version compile works fine. The release version does not.

All it gives me is a program exception - access violation. #157.

Ideas on what to try?

Linda

Try turning off optimization on the release compile. If that works, you can raise the level in increments until you find the highest optimization setting that will work.

Cheers,

Rich

[Jugoslav_Dujic]

Quoting - linda@lawrie.com

I hate these problems.

I have a mixed project -- has some c libraries, modules, etc.

Both debug and release work fine inside the Visual Studio environment.

Outside, the debug version compile works fine. The release version does not.

All it gives me is a program exception - access violation. #157.

Ideas on what to try?

Uninitialized variables? Try /Qtrapuv (Fortran/Data/Initialize stack variables...), maybe it helps reproduce the problem in debugger. [If you use ALLOCATABLEs a lot, I can offer a trick which automagically initializes all allocatables to NaN/large integer].

After that, try compiling the release version with debug information. When/if it crashes, try just-in-time debugging. (If Murphy's law works, you won't be able to reproduce the problem because debug information alters the conditions :-( ).

If it fails, you'll probably have to resort to WRITE statements to try at least locating the subroutine/block with the problem. After you find out at least the rough location, use debugger and/or staring method to see the exact culprit.

[lklawrie]

Compiling with debug information helped me find a different problem.

Now resorting to write statements. I think the problem is in one of the c modules -- since all the other test suite files (around 300) run fine but this one.

Thanks for the advice.

Linda

[lklawrie]

I have fixed the problem though I'm not quite sure what it was or what caused it.

But, found some developer additions that were unnecessary and removed them which helped.

Linda