BUG: MSDEV Crashes if Same PDB Name Used for Compiler and LinkerLast reviewed: October 29, 1997Article ID: Q172892 |
The information in this article applies to:
SYMPTOMSWhen 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.-or-
MSDEV.EXE - Application error. The exception unknown software exception (0xc00000fd) occurred in the application at location 0x1030837b. CAUSEThe /pdbtype:sept linker option specifies that the debug information generated by the compiler and the linker be kept in separate pdb files. Since 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.
RESOLUTIONTurn off /pdbtype:sept. To do this, click Project, click Options, click the Link tab, select the Debug category, and deselect the "Separate types" check box. -or- Do not use the same pdb file name for linker and compiler output.
STATUSMicrosoft 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/pdbtype:sept is the default in a Developer Studio project.
Steps to Reproduce Behavior
|
Additional query words: access violation AV crash GPF IPF fault
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |