BUG: Access Violation Opening a Workspace of Type Makefile

ID: Q154111

The information in this article applies to:

Microsoft Visual C++, 32-bit Editions, versions 4.0, 4.1, 4.2, 5.0, 6.0

SYMPTOMS

Sometimes when you open a Visual C++ generated makefile that has been modified (either by you or corrupted by the system), Developer Studio generates a fatal application error (illegal operation, access violation, gpf, page fault).

CAUSE

Visual C++ uses the makefile to store project information and is sensitive to changes in the format of the file.

RESOLUTION

When you edit a makefile generated by Visual C++, delete the first few lines of the makefile. These lines are comments that Visual C++ uses to identify makefiles that are generated by Visual C++. When those lines are deleted, Visual C++ will not attempt to parse the makefile.

If your makefile has become corrupted (you get a fatal error and you haven't edited the makefile), then you must restore the makefile from a backup, if you have one, or re-create the project.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

The point at which Developer Studio crashes varies. Sometimes the makefile is partially read in and then the crash occurs. Sometimes the makefile is partially read in and then you are be prompted:

This makefile was not generated by Developer Studio. Continuing will create a new Developer Studio workspace to wrap this makefile.

After you click Yes, the crash occurs.

NOTE: In Visual C++, version 5.0 and later, after you click Yes, a workspace with only one project is generated. The project has only one file, which is the makefile. This means that the makefile is not being parsed at all. (The comments are not being taken into account.) However, this does not crash Developer Studio.

Additional query words: gpf crash access violation

Keywords : kbide kbVC kbVC410bug kbVC420bug kbVC500bug kbVC600bug kbGrpDSTools
Version : 4.00 4.10 4.20 5.00 6.00
Platform : NT WINDOWS
Issue type : kbbug