Comments on: Symbol file warnings in WinDbg 6.8.0004.0 https://www.dumpanalysis.org/blog/index.php/2007/11/08/symbol-file-warnings-in-windbg-6800040/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Wed, 06 May 2026 18:22:43 +0000 http://wordpress.org/?v=2.3.3 By: Taed https://www.dumpanalysis.org/blog/index.php/2007/11/08/symbol-file-warnings-in-windbg-6800040/#comment-419001 Taed Sun, 05 Feb 2012 00:00:42 +0000 https://www.dumpanalysis.org/blog/index.php/2007/11/08/symbol-file-warnings-in-windbg-6800040/#comment-419001 I just ran into this and did an upgrade, and it does NOT happen with 6.12.0002.633. Yay! I just ran into this and did an upgrade, and it does NOT happen with 6.12.0002.633. Yay!

]]> By: Manvendra Kumar https://www.dumpanalysis.org/blog/index.php/2007/11/08/symbol-file-warnings-in-windbg-6800040/#comment-67842 Manvendra Kumar Wed, 11 Mar 2009 06:22:23 +0000 https://www.dumpanalysis.org/blog/index.php/2007/11/08/symbol-file-warnings-in-windbg-6800040/#comment-67842 Also Happens with windbg:6.11.0001.402 x86 ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: kernel32!pNlsUserInfo *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: kernel32!pNlsUserInfo *** *** *** ************************************************************************* but when i checked for symbols it was loaded. 0:000> lmv m kernel32 start end module name 77e40000 77f42000 kernel32 (pdb symbols) c:\symcache\kernel32.pdb\7FD4C98964054C24B2C472948D829DF52\kernel32.pdb Loaded symbol image file: kernel32.dll Image path: C:\WINNT\system32\kernel32.dll Image name: kernel32.dll Timestamp: Wed Apr 18 21:55:36 2007 (46264680) CheckSum: 001083FC ImageSize: 00102000 File version: 5.2.3790.4062 Product version: 5.2.3790.4062 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: kernel32 OriginalFilename: kernel32 ProductVersion: 5.2.3790.4062 FileVersion: 5.2.3790.4062 (srv03_sp2_gdr.070417-0203) FileDescription: Windows NT BASE API Client DLL LegalCopyright: © Microsoft Corporation. All rights reserved. Also Happens with windbg:6.11.0001.402 x86

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

but when i checked for symbols it was loaded.
0:000> lmv m kernel32
start end module name
77e40000 77f42000 kernel32 (pdb symbols) c:\symcache\kernel32.pdb\7FD4C98964054C24B2C472948D829DF52\kernel32.pdb
Loaded symbol image file: kernel32.dll
Image path: C:\WINNT\system32\kernel32.dll
Image name: kernel32.dll
Timestamp: Wed Apr 18 21:55:36 2007 (46264680)
CheckSum: 001083FC
ImageSize: 00102000
File version: 5.2.3790.4062
Product version: 5.2.3790.4062
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: kernel32
OriginalFilename: kernel32
ProductVersion: 5.2.3790.4062
FileVersion: 5.2.3790.4062 (srv03_sp2_gdr.070417-0203)
FileDescription: Windows NT BASE API Client DLL
LegalCopyright: © Microsoft Corporation. All rights reserved.

]]> By: Paul https://www.dumpanalysis.org/blog/index.php/2007/11/08/symbol-file-warnings-in-windbg-6800040/#comment-61908 Paul Fri, 09 Jan 2009 21:10:57 +0000 https://www.dumpanalysis.org/blog/index.php/2007/11/08/symbol-file-warnings-in-windbg-6800040/#comment-61908 Also happens in WinDbg 6.10.3.233 Appears to be a known WinDbg problem that still needs to be fixed: http://www.eggheadcafe.com/software/aspnet/33050264/symbols-mismatch.aspx Also happens in WinDbg 6.10.3.233

Appears to be a known WinDbg problem that still needs to be fixed:
http://www.eggheadcafe.com/software/aspnet/33050264/symbols-mismatch.aspx

]]>