Article ID: 148220 - Last Review: August 24, 2005 - Revision: 1.2 PRB: Debugger Reports "WARNING: symbols checksum is wrong"This article was previously published under Q148220 SYMPTOMS When debugging a Win32 application on the uniprocessor
version of Windows NT, WinDbg displays warning messages that say: *** WARNING: symbols checksum is wrong 0x0005e382 0x00062261 for
D:\WINNT\symbols\dll\NTDLL.DBG. The actual path for Ntdll.dbg will vary depending on where Windows NT is installed on your system. This warning may be generated for symbol files of other system files such as Kernel32.dll also. CAUSE WinDbg verifies that the checksum of the DLL matches the
checksum stored in the corresponding debugging symbol (.dbg) file to warn you
when your debugging symbols don't match the modules being debugged. If the
symbols truly are mismatched, then WinDbg will show incorrect function names
when you obtain stack traces and set breakpoints. During installation, Windows NT runs with the multiprocessing kernel and system files. At the end of the installation procedure on uniprocessor Intel x86 machines, the setup program modifies the kernel and other system files to remove spin lock code needed only on multiprocessor systems. Because the debugging symbol files were created with the multiprocessing system files, this modification causes the checksums of system files to differ from the checksums in the debugging symbol files. It does not change the file size of the system DLLs, any system code, or the addresses of system entry points. The symbol files are still correct, but because the checksums differ, WinDbg reports a warning. RESOLUTION Although this message is benign and can be ignored, this
issue is resolved in the latest debugging tools. For more information on these
tools, see the following Microsoft Web site: http://www.microsoft.com/whdc/devtools/ddk/default.mspx
(http://www.microsoft.com/whdc/devtools/ddk/default.mspx)
STATUS This behavior is by design. | Article Translations
|
Back to the top
