error when linking with /check /undef

I have some Fortran code that runs and produces sensible output when I use the following commands:

ftn95 /intl /dreal /64 CVA_ascii_image_n_B_W.for > ftn_compile.out slink64 CVA_ascii_image_n_B_W.obj CVA_ascii_image_n_B_W.exe

However, when I attempt to run the same code with

ftn95 /intl /dreal /64 /check /undef CVA_ascii_image_n_B_W.for > ftn_compile.out slink64 CVA_ascii_image_n_B_W.obj CVA_ascii_image_n_B_W.exe

the program doesn't load correctly into the Silverfrost 64-bit Debugger, and I get the error message

Call Stack Error: Access Violation writing address 0x0000000002661000

000000000040127F

Any suggestions as to what I need to change so that the program runs?

Norm Campbell

Norm

Can you send or post the Fortran code that produces this error report.

Better still, provide the shortest program that demonstrates the failure.

Thank you Paul

I've sent the code via email.

Please let me know when you receive it.

Norm

I have received your code. For me, FTN95 fails when trying to compile the code for 64 bits but with a different outcome. Which version of FTN95 are you using and can you confirm that it is for 64 bits?

Norm

After fixing numerous error reports of the form 'error 694 - Spurious comma at end of line', your code compiles successfully for me but it then fails to link, presumably because of a missing INCLUDE.

Maybe you have sent me the wrong program.

Hi Paul

There is a line

  common / eig_det / det

in subr cvpgei

called from cvpcvu called from cvscvp called from CVA_successive_projections.

When I comment that out, the code links and runs under the debugger.

Norm

Does that mean that there is no longer a problem?

I've found the cause of the problem, and fixed it, but I am curious as to why a superfluous common statement should cause the debugger to fail to operate.

Norm

I don't know why it failed for you.