FEAP installation under debugger mode

[M. Kurdi]

Hello. I want to change my FEAP installation from "release" to "debug". This will allow me to better debug macros I have built. Under the installation manual the difference is to change from release to debug and set the run time in the compiler to not check array bounds. I set these but I get many errors and could not build. I am using microsoft visual studio 2010 and Intel Fortran compiler. Do you have any recommendation for installing the debugging mode?
Below is summary of these errors.  Thanks for your help.

1>C:\feap\ver84\elements\couple3d\sld3d1tm.f(358): error #6633: The type of the actual argument differs from the type of the dummy argument.   [NEL]
1>C:\feap\ver84\elements\couple3d\sld3d1tm.f(358): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.   [NEL]
1>C:\feap\ver84\elements\couple3d\sld3d1tm.f(358): error #8284: If the actual argument is scalar, the dummy argument shall be scalar unless the actual argument is of type character or is an element of an array that is not assumed shape, pointer, or polymorphic.   
1>compilation aborted for C:\feap\ver84\elements\couple3d\sld3d1tm.f (code 1)
1>umacr20.f
1>C:\feap\ver84\user\umacr20.f(100): error #6552: The CALL statement is invoking a function subprogram as a subroutine.   [PALLOC]
1>C:\feap\ver84\user\umacr20.f(138): error #6552: The CALL statement is invoking a function subprogram as a subroutine.   [PALLOC]
1>compilation aborted for C:\feap\ver84\user\umacr20.f (code 1)
1>psetexim.f
1>C:\feap\ver84\program\psetexim.f(57): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.   [NN]
1>compilation aborted for C:\feap\ver84\program\psetexim.f (code 1)
1>fld3d1tm.f
1>C:\feap\ver84\elements\couple3d\fld3d1tm.f(528): error #6633: The type of the actual argument differs from the type of the dummy argument.   [NEL]
1>C:\feap\ver84\elements\couple3d\fld3d1tm.f(528): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.   [NEL]
1>C:\feap\ver84\elements\couple3d\fld3d1tm.f(528): error #8284: If the actual argument is scalar, the dummy argument shall be scalar unless the actual argument is of type character or is an element of an array that is not assumed shape, pointer, or polymorphic.   
1>compilation aborted for C:\feap\ver84\elements\couple3d\fld3d1tm.f (code 1)
1>fld3d2tm.f
1>C:\feap\ver84\elements\couple3d\fld3d2tm.f(692): error #6633: The type of the actual argument differs from the type of the dummy argument.   [NEL]
1>C:\feap\ver84\elements\couple3d\fld3d2tm.f(692): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.   [NEL]
1>C:\feap\ver84\elements\couple3d\fld3d2tm.f(692): error #8284: If the actual argument is scalar, the dummy argument shall be scalar unless the actual argument is of type character or is an element of an array that is not assumed shape, pointer, or polymorphic.   

[Prof. R.L. Taylor]

This is surprising as the parameter NEL comes through a common block /eldata so types should not be an issue.  Is this the only routine that is causeing problems?  If so, I would suggest  making a dummy routine to replace it as it is not really fully implemented at this time.

[FEAP_Admin]

I tried to build a debug version but my Intel+VS combination crashes with a fatal compiler error (i.e. the compiler software has a bug in it).
So it impossible for us to assist on this matter.

I could suggest that you install cygwin on your windows machine and then you can compiler a debug version and use gdb as your debugger.

[M. Kurdi]

Thanks for investing time to check.

[xushuhao]

Hello. I want to change my FEAP installation from "release" to "debug". This will allow me to better debug macros I have built. Under the installation manual the difference is to change from release to debug and set the run time in the compiler to not check array bounds. I set these but I get many errors and could not build. I am using microsoft visual studio 2010 and Intel Fortran compiler. Do you have any recommendation for installing the debugging mode?
Below is summary of these errors.  Thanks for your help.

1>C:\feap\ver84\elements\couple3d\sld3d1tm.f(358): error #6633: The type of the actual argument differs from the type of the dummy argument.   [NEL]
1>C:\feap\ver84\elements\couple3d\sld3d1tm.f(358): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.   [NEL]
1>C:\feap\ver84\elements\couple3d\sld3d1tm.f(358): error #8284: If the actual argument is scalar, the dummy argument shall be scalar unless the actual argument is of type character or is an element of an array that is not assumed shape, pointer, or polymorphic.   
1>compilation aborted for C:\feap\ver84\elements\couple3d\sld3d1tm.f (code 1)
1>umacr20.f
1>C:\feap\ver84\user\umacr20.f(100): error #6552: The CALL statement is invoking a function subprogram as a subroutine.   [PALLOC]
1>C:\feap\ver84\user\umacr20.f(138): error #6552: The CALL statement is invoking a function subprogram as a subroutine.   [PALLOC]
1>compilation aborted for C:\feap\ver84\user\umacr20.f (code 1)
1>psetexim.f
1>C:\feap\ver84\program\psetexim.f(57): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.   [NN]
1>compilation aborted for C:\feap\ver84\program\psetexim.f (code 1)
1>fld3d1tm.f
1>C:\feap\ver84\elements\couple3d\fld3d1tm.f(528): error #6633: The type of the actual argument differs from the type of the dummy argument.   [NEL]
1>C:\feap\ver84\elements\couple3d\fld3d1tm.f(528): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.   [NEL]
1>C:\feap\ver84\elements\couple3d\fld3d1tm.f(528): error #8284: If the actual argument is scalar, the dummy argument shall be scalar unless the actual argument is of type character or is an element of an array that is not assumed shape, pointer, or polymorphic.   
1>compilation aborted for C:\feap\ver84\elements\couple3d\fld3d1tm.f (code 1)
1>fld3d2tm.f
1>C:\feap\ver84\elements\couple3d\fld3d2tm.f(692): error #6633: The type of the actual argument differs from the type of the dummy argument.   [NEL]
1>C:\feap\ver84\elements\couple3d\fld3d2tm.f(692): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface.   [NEL]
1>C:\feap\ver84\elements\couple3d\fld3d2tm.f(692): error #8284: If the actual argument is scalar, the dummy argument shall be scalar unless the actual argument is of type character or is an element of an array that is not assumed shape, pointer, or polymorphic.   

This problem remains. Has anyone solved it yet?

[Prof. S. Govindjee]

What version of FEAP are you using?   You should not see such compiler errors with the current version of FEAP.