Article ID: 109880
Article Last Modified on 10/24/2003
APPLIES TO
- Microsoft FORTRAN PowerStation 1.0 Standard Edition
- Microsoft Fortran PowerStation 1.0a for MS-DOS
- Microsoft FORTRAN PowerStation 32
This article was previously published under Q109880
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:
Note that the filename refers to the include file FLIB.FD, but the line number (7) correctly indicates the location in the main program where the error occurred.
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
Additional query words: 1.00 5.10
Keywords: kberrmsg kbbug kbfix kblangfortran KB109880