BUG: Access Violation Opening a Workspace of Type Makefile

The information in this article applies to:

• Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2

SYMPTOMS

Sometimes when opening a Visual C++ generated makefile that has been modified (either by you or corrupted by the system), Developer Studio will generate 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 editing 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. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The point at which Developer Studio crashes varies. Sometimes the makefile will be partially read in and the crash will occur. Sometimes the makefile will partially be read in and you will 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 will occur.