BUG: CVW 3.x and FORTRAN DLLs: Stack Trace Hangs Machine

Last reviewed: February 16, 1996
Article ID: Q85164
The information in this article applies to:
  • Microsoft FORTRAN for MS-DOS, version 5.1
  • Microsoft FORTRAN for OS/2, version 5.1

SYMPTOMS

Using Microsoft Codeview for Windows versions 3.x under Windows 3.1 to debug Microsoft FORTRAN 5.1 Windows DLLs that have been called by C applications can hang the machine if the CALL menu is selected or the stack trace command, K, is entered in the command window.

CAUSE

There is a problem in the CodeView for Windows FORTRAN expression evaluator that is incorrectly accessing the stack.

RESOLUTION

If a stack trace is desired, enter the command

   use c

in the command window. This will cause CVW to use the C expression evaluator. To return using the FORTRAN expression evaluator type

   use fortran

in the command window.

STATUS

Microsoft has confirmed this to be a problem in FORTRAN version 5.1.

This is not an issue in FORTRAN PowerStation.

MORE INFORMATION

To duplicate this problem, build the MULMIX_D project that is provided in the FORTRAN 5.1 samples subdirectory. There is a makefile that is provided called MULMIX_D.MAK. The makefile assumes that C 6.0 will be used. Using C/C++ 7.0 to build the application and DLL avoids the problem because there is no FORTRAN expression evaluator for the 4.0 versions of CV or CVW which are provided with C/C++ 7.0.


Additional reference words: 5.10
KBCategory: kbtool kbbuglist
KBSubCategory: CvwIss


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