BUG: Equivalence and Non-Common Block Variable Cause ASSERT

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

SYMPTOMS

Assigning a value to an equivalenced variable not part of a common block in an internal subroutine when the associated equivalenced variable is part of a common block causes the following compile-time ASSERT failure message to be generated:

   Assertion failed: base->key.be_key != 0, file err_genex.c, line 2828
   abnormal program termination

RESOLUTION

Do one of the following to work around the problem:

  • Redeclare the common block and equivalence in the internal procedure.

    -or-

  • Do not assign a value to the non-common block equivalenced variable.

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

Sample Code to Illustrate Problem

! Compile options needed: none

      program test
          real r
          integer i
          common /theblock/ i
          equivalence (r,i)
          call b
          print *, r
      contains
          subroutine b
! uncomment the next 4 lines for work-around
!              real r
!              integer i
!              common /theblock/ i
!              equivalence (r,i)
              r = 1.0          ! This line causes an ASSERT failure
          end subroutine b
      end program test


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