Article ID: 122262
Article Last Modified on 10/23/2003
APPLIES TO
- The Microsoft Linker (LINK.EXE), when used with:
- Microsoft Visual C++ 2.0 Professional Edition
This article was previously published under Q122262
SYMPTOMS
When building a project with debug information under low disk space conditions (on either the project drive or the TEMP\ directory drive), the following error may be generated:
When linking incrementally, the following warning may precede the LNK1200 error:
CAUSE
When LINK fails because of low disk space conditions, corruption of the .PDB file associated with the target may occur. Because .PDB files are updated incrementally, subsequent builds that update the .PDB file for the target will fail and give the LNK1200 error.
RESOLUTION
Having LINK generate a new .PDB file for the target will alleviate the problem. The resolution has two steps:
- Delete the (corrupt) .PDB file for the target.
- Free up enough disk space, so that there is sufficient room for the new .PDB file and the updated target.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft 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 LNK4081 warning is warning you that there is not enough disk space for the Linker to update the .ILK file or write out a new one if one doesn't already exist.
Additional query words: 2.00 2.50
Keywords: KB122262
