BUG: Unused Local Variables Are Unavailable in the Debugger

 Last reviewed: March 8, 1996
Article ID: Q148201
The information in this article applies to:
  • Microsoft Fortran PowerStation for Windows 95 and Windows NT, version 4.0

SYMPTOMS

Local variables flagged by the compiler as unused become unavailable in the debugger even if they have been initialized with the DATA statement.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Using Developer Studio build the following sample code. After building the project, start a debugging session. On the Build menu, click Debug, and then click Step Into. The variables "A" and "B" are not displayed in the locals window even though they have been initialized with the integer values of "1" and "2" respectively.

Sample Code

C Compile options needed: /Zi 

      INTEGER A, B

      DATA A / 1 /
      DATA B / 2 /

      PRINT *, 'HELLO'
      END

Additional reference words: 4.00
KBCategory: kbprg kbbuglist
KBSubcategory: FORTLngIss

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: March 8, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.