FIX: Improper Debug Stepping in Routines w/ ENTRY Points

Last reviewed: September 18, 1997
Article ID: Q109875

1.00 WINDOWS NT kbtool kbfixlist

The information in this article applies to:

- Microsoft FORTRAN PowerStation 32 for Windows NT, version 1.0

SYMPTOMS

In an attempt to step into a subroutine through an entry point, the lines appear to be executed out of order. In reality they are not executed out of sequence; the sequence of events appear to be this:

The first step into the entry point goes to the END statement.

2. The second step goes to the SUBROUTINE statement. 3. The third step goes to the first executable line in the subroutine but

   doesn’t execute it.

4. The fourth step goes to the END statement again. 5. The fifth step goes to the first executable line in the entry point.

From here on the stepping and execution sequence is correct.

CAUSE

This problem is caused by the compiler putting out improper line number information for the entry point.

RESOLUTION

There is currently no work around for this problem.

STATUS

Microsoft has confirmed this to be a problem in Microsoft FORTRAN PowerStation 32 for Windows NT, version 1.0. This problem was fixed in FORTRAN PowerStation version 4.0.

Additional reference words: 1.00
KBCategory: kbtool kbbuglist kbfixlist
KBSubcategory: WBDebug
Keywords : WBDebug kbbuglist kbfixlist kbtool
Version : 1.00
Platform : NT WINDOWS
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.