FIX: Incorrect $DEBUG Reference to Include File

MS-DOS     | WINDOWS NT

The information in this article applies to:

• Microsoft FORTRAN PowerStation for MS-DOS, version 1.0 and 1.0a
• Microsoft FORTRAN PowerStation 32 for Windows NT, version 1.0

SYMPTOMS

Under some circumstances, a $DEBUG message may incorrectly give the name of an include file instead of the name of the program where the trapped run- time error occurred. For example, the code sample shown below deliberately references the array "nums" beyond its bounds. With the $DEBUG metacommand at the top of the program, the run-time error is reported as:

   C:\FPSNT\INCLUDE/flib.fd(7) : run-time error F6096: $DEBUG
   - array subscript expression out of range

   Execution traceback:
                from main program in C:\FPSNT\INCLUDE/flib.fd(7)

This can also happen with user-defined include files.

RESOLUTION

If the $DEBUG metacommand is moved to below the include statements, then the correct filename will be referenced.

STATUS

Microsoft has confirmed this to be a problem in the products listed at the beginning of this article. This problem was corrected in FORETRAN PowerStation 32, version 4.0.

MORE INFORMATION

This situation also exists with Microsoft FORTRAN version 5.1.

Sample Code

C Compile options needed: NONE $DEBUG

      include 'flib.fi'
      include 'flib.fd'
      integer*4 nums(7)
      do i = 1, 10
        nums(i) = i
        write(*,*) nums(i)
      end do
      end