Basic Troubleshooting

The following lists some of the most basic problems you can encounter during application development and gives suggestions for troubleshooting:

Controlling Compiler Diagnostic Warning and Error Messages

You can use compiler options to control the diagnostic messages issued by the compiler. For example, the -WB compiler option turns compile time bounds errors into warnings. The -warn keyword option controls warnings issued by the compiler. It supports a wide range of values. Some of these are as follows:

[no]alignments -- Determines whether warnings occur for data that is not naturally aligned.

[no]declarations -- Determines whether warnings occur for any undeclared symbols.

[no]errors -- Determines whether warnings are changed to errors.  

[no]general -- Determines whether warning messages and informational messages are issued by the compiler.

[no]interfaces -- Determines whether warnings about the interfaces for all called SUBROUTINEs and invoked FUNCTIONs are issued by the compiler.

[no]stderrors -- Determines whether warnings about Fortran standard violations are changed to errors.  

[no]truncated_source -- Determines whether warnings occur when source exceeds the maximum column width in fixed-format files.

For more information, see the -warn keyword compiler option.

You can perform compile-time procedure interface checking between routines with no explicit interfaces present. To do this, generate a module containing the interface for each compiled routine (using the -gen-interfaces option) and check implicit interfaces (using the -warn interfaces option.)