FIX: Protection Violation, Application Error, From COMMON Name

 Last reviewed: September 10, 1997
Article ID: Q27558
4.10 5.00 5.10 | 5.10 
OS/2           | MS-DOS
kbprg kbfixlist kbbuglist kberrmsg kbcode

The information in this article applies to:

  • Microsoft FORTRAN for OS/2, versions 4.1, 5.0, 5.1
  • Microsoft FORTRAN for MS-DOS, version 5.1

SYMPTOMS

An attempt to run an application fails and the corresponding message below appears on the screen. In FORTRAN for OS/2, the following message appears: 

   A program caused a Protection Violation.
If the application compiled as a QuickWin application, the following message appears: 

   Unexpected Application Error

CAUSE

The name of a COMMON block in the application ends with the letters "code." The compiler confuses the code and data segments that have similar names. When the application writes to the COMMON block, the generated code writes into a code segment.

RESOLUTION

To work around this problem, modify the source code to rename the COMMON block. The last four letters of the name cannot be "code."

STATUS

Microsoft has confirmed this to be a problem in FORTRAN versions 4.1, 5.0, and 5.1. This problem was corrected in FORTRAN PowerStation.

MORE INFORMATION

The following code example demonstrates this problem.

Sample Code

      COMMON /PCODE/ I
      I = 7
      END

Additional reference words: 4.10 5.00 5.10
KBCategory: kbprg kberrmsg kbfixlist kbbuglist kbcode
KBSubcategory: FLIss
Solution Type : kbfix

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: September 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.