FIX: MSDEV Crashes If Same PDB Name Used for Compiler and Linker (172892)
The information in this article applies to:
- The Integrated Debugger, when used with:
- Microsoft Visual C++, 32-bit Enterprise Edition 5.0
- Microsoft Visual C++, 32-bit Professional Edition 5.0
This article was previously published under Q172892 SYMPTOMS
When the pdb file generated by the compiler has the same name as the pdb
file generated by the linker, and the /pdbtype:sept option is set,
Developer Studio may crash if you select Debug.StepInto. It may also crash
if you set a breakpoint and select Debug.Go.
Following are examples of possible error messages:
MSDEV caused a stack fault in module MSPDB50.DLL at 015f:1030493b.
MSDEV.EXE - Application error. The exception unknown software exception
(0xc00000fd) occurred in the application at location 0x1030837b.
CAUSE
The /pdbtype:sept linker option specifies that the debug information
generated by the compiler and the linker be kept in separate pdb files.
Because the same pdb file name is used, the linker overwrites the pdb file
generated by the compiler without copying the compiler debug info as well.
When the debugger attempts to use this file it goes into infinite recursion
and eventually the stack overflows and causes Developer Studio to crash.
RESOLUTION
Use one of the following workarounds: - Turn off /pdbtype:sept. To do this, on the Project menu, click Options, click the
Link tab, select the Debug category, and clear the Separate types check box.
- Do not use the same pdb file name for linker and compiler output.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. This problem was corrected in Visual C++ version 6.0 for Windows.
Modification Type: | Major | Last Reviewed: | 11/18/2003 |
---|
Keywords: | kbBug kbDebug kbfix kbide kbVC600fix KB172892 |
---|
|