Re: Fortran module checking

Eigenvector wrote:

I'm a serious newbie to Fortran and am asking this because I'm being forced to help debug another unwilling person's code. Forgive the lack of understanding.

The code that I'm interested in uses modules to retrieve variable names for the main code. Essentially there is a variable.f containing all the code variables which is turned into a .mod file - that is then called by main.f with a USE statement.

It would appear through my debugger (idebug) that attempts to call code in that .mod file are returning segmentation faults. But I can't prove that and the developer is balking. So I'm looking for ways to demonstrate that the contents of the .mod file are being included in the finished product and available to the executable - that the syntax is proper. He's a developer and believes my system is in error, I'm a Sys Ad and believe his code is in error so I'm trying to establish the validity of my position by demonstrating that either I'm right or wrong.

Is it as simple as (mind you I'm using xlf90)
! variable.f psuedocode
variable1 = tag1, tag2

xlf90 variable.f -o variable.mod (I'm paraphrasing here)

! main.f psuedocode
use tag1="Hello"
use tag2="Hi"

xlf90 main.f -o program.exe

Or are there compile options that should be invoked to ensure that USE statements get included into the main code?



I'm not an expert, but this doesn't look anything like the way I've seen modules used. First, show the code that defines the module. It should be something like:

module foo
integer :: x,y
character(10) :: a,b
end module

In the places where the module foo is used you should just have:

use foo

then the variables x,y,a,b are made available.
.

Relevant Pages

  • Fortran module checking
    ... understanding. ... and the developer is balking. ... Is it as simple as (mind you I'm using xlf90) ... variable.f psuedocode ...
    (comp.lang.fortran)
  • Re: Fortran module checking
    ... and the developer is balking. ... Is it as simple as (mind you I'm using xlf90) ... variable.f psuedocode ... Or are there compile options that should be invoked to ensure that USE ...
    (comp.lang.fortran)
  • Re: Fortran module checking
    ... variable.f psuedocode ... xlf90 variable.f -o variable.mod (I'm paraphrasing here) ...
    (comp.lang.fortran)