BUG: Incorrect Use of #pragma Pack Causes C1001 Errors

Last reviewed: July 24, 1997
Article ID: Q119873
The information in this article applies to:
  • The C/C++ Compiler (CL.EXE) included with: - Microsoft Visual C++, 32-bit Edition, versions 1.0, 2.0, 4.0, 4.1,

         4.2, 5.0
    

SYMPTOMS

When compiling code that uses #pragma pack() to pop an ID that has not been pushed after successfully popping an ID that was pushed, the compilers listed above will generate:

   fatal error C1001: INTERNAL COMPILER ERROR

In addition, this error will be followed by a message similar to

    (compiler file 'msc1.cpp', line 902)
    Please choose the Technical Support command on the Visual C++
    Help menu, or open the Technical Support help file for more information

RESOLUTION

Pop only IDs that have been previously pushed onto the compiler's internal stack.

STATUS

Microsoft has confirmed this to be a bug in the 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

The following sample code demonstrates the bug:

Sample Code

   /* packfail.c

   Compile options needed: none
   */

   #pragma pack(push, a)
   #pragma pack(push, b, 4)
   #pragma pack(pop, b)
   #pragma pack(pop, value)


Additional query words: 8.00 9.00 buglist1.00 buglist2.00 buglist8.00
buglist9.00 10.00 10.10 10.20

Keywords : CLIss vcbuglist400 vcbuglist500
Version : 1.0 2.0 4.0 4.1 4.2 5.0
Platform : NT WINDOWS
Issue type : kbbug


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