BUG: Assertion Failure with ERR= and END= in READ Statement

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

SYMPTOMS

Using the err= and end= options together in a READ statement and performing a formatted READ using an integer expression in a FORMAT statement causes the following compile-time ASSERT failure message to be generated:

   Assertion failed: 0, file err_genex.c, line 6143

RESOLUTION

Use literal constants instead of integer expressions with edit descriptors in FORMAT statements.

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 and Workaround

! Compile options needed: none

      integer, parameter :: lenrec = 25
      character*25 rec

      open (unit=1,file='test.dat',status='old')
      read (1,100,end=500,err=500) rec
100 format (a<lenrec>) ! Comment for workaround ! Uncomment the next line for workaround
! 100  format (a25)       ! Use literal values with edit descriptors
500 continue
      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 28, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.