Knowledge Base

BUG: Equivalence and Non-Common Block Variable Cause ASSERT

PSS ID Number: 149147

Article Last Modified on 11/6/1999


The information in this article applies to:


This article was previously published under Q149147

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 query words: 4.00

Keywords: kbLangFortran KB149147
Technology: kbAudDeveloper kbFORTRANPower400NT kbFortranSearch kbZNotKeyword8