I am trying to make sense out of this stack trace after my program crashed: MSPST32.DLL!35cc9861() [Frames below may be incorrect and/or missing, no symbols loaded for MSPST32.DLL] USER32.dll!_InternalCallWinProc@20() + 0x28 bytes USER32.dll!_UserCallWinProcCheckWow@32() + 0xb7 bytes USER32.dll!_CallWindowProcAorW@24() + 0x51 bytes USER32.dll!_CallWindowProcW@20() + 0x1b bytes MFC80U.DLL!_AfxActivationWndProc() + 0x11c bytes USER32.dll!_InternalCallWinProc@20() + 0x28 bytes > USER32.dll!_UserCallWinProcCheckWow@32() + 0xb7 bytes USER32.dll!_DispatchMessageWorker@8() + 0xdc bytes USER32.dll!_DispatchMessageW@4() + 0xf bytes MFC80U.DLL!AfxInternalPumpMessage() + 0x3e bytes MFC80U.DLL!CWinThread::Run() + 0x54 bytes MFC80U.DLL!AfxWinMain() + 0x69 bytes MyProgram.exe!__tmainCRTStartup() Line 589 + 0x1c bytes C kernel32.dll!_BaseProcessStart@4() + 0x23 bytes Are the debug symbols for MSPST32.DLL available? I am using the symbol servers: http://msdl.microsoft.com/download/symbols http://www.microsoft.com/whdc/DevTools/Debugging/symbols.mspx Thanks, Frank
Hi Frank, > I am trying to make sense out of this stack trace after my program > crashed: > > MSPST32.DLL!35cc9861() > [Frames below may be incorrect and/or missing, no symbols loaded for > MSPST32.DLL] USER32.dll!_InternalCallWinProc@20() + 0x28 bytes ... > Are the debug symbols for MSPST32.DLL available? Unfortunately not. It is askes from time to time but Microsoft claims it is too much work to strip the debug symbols of third party symbols and other stuff which should not be published. Please Microsoft, listen to us Office developers, it would make tracking down errors so much easier with public symbols for Office apps. Please reconsider making them available. -- SvenC
