apogee-software apogee compilers c & c++ & fortran 77 & fortran 90 User Manual

Page of 223
Apogee Software, Inc.
Page 172 Apogee User’s Manual
For example, suppose you have five routines:
a
,
b
,
c
,
d
, and
e
.  When all five are
processed with VAST, the program produces incorrect results or dies.  Try running
VAST again, but only on routines
a
 and
b
.  If they succeed, then the problem is in
c
,
d
,
or
e
.  If they fail, try with just routine
a
, and so on.  By breaking the list of suspects into
approximate halves for each test, you can identify fairly quickly which routine or
routines cause the failure.  Leave the problematic routines out of future VAST runs.
5) If you have link errors, ensure that the link step loaded all the libraries needed for all
parts of the program.  Be sure to use the appropriate
-Xvast
 option at link-time as
well as compile time, as this will identify which libraries are needed.
A link failure may also occur because VAST failed while processing a file, and the
routines that came after the point of failure in that file were not copied to the compile
file.  Determine the reason that VAST failed, and try relinking.
6) If the compiler issues a syntax error on a transformed program, compare the source
code with the transformed code.  VAST detects and flags some runtime errors,
especially in I/O statements, at compilation time.