PRB: Using the Stop Build Command May Corrupt Output Files

 Last reviewed: July 24, 1997
Article ID: Q168382
The information in this article applies to:
  • Microsoft Visual C++ for Windows, 16-bit edition, version 1.52
  • Microsoft Visual C++, 32-bit Editions, versions 2.0, 2.1, 2.2, 4.0, 4.0a, 4.1, 4.2, 4.2b, 5.0

SYMPTOMS

NOTE: This information has not been confirmed by Microsoft. The information in this article is provided as-is and is subject to change without notice.

In some cases, when you use the Stop Build command while you are building a project, files that are created by the build process are corrupted. Some of the problems reported to Microsoft, but unconfirmed, include zero-sized output files (PDB, BSC, OBJ, etc.) and possible loss of data in project source files.

RESOLUTION

This problem is difficult to reproduce, and occurs very rarely. However, it is always a good idea to maintain a backup of your project to be safe.

STATUS

Microsoft is researching this problem and will post new information in the Microsoft Knowledge Base as it becomes available.

Keywords : CodeGen VWBIss
Version : 1.52 2.0 2.1 2.2 4.0 4.0a 5.0
Platform : NT WINDOWS
Issue type : kbprb

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.