The following additional symbols were downloaded automatically while the command was running. This time ld * command also ran fine without any errors. I found that C:\microsoftsymbols\ntdll.pdb\F7024C7F15FE4BEA992FF38BE58AC11C2\ntdll.pdb was downloaded automatically. Now, on opening C:\foo\Foo.exe from the 'File > Open Executable' menu, I got no errors. This time I set the symbol path as: SRV*C:\MicrosoftSymbols* C:\MySymbols However, the ld * command showed fewer errors this time. On opening C:\foo\Foo.exe from the 'File > Open Executable' menu, I got the same error mentioned in the previous section. In WinDbg, I set the symbol path as: C:\Symbols C:\MySymbolsĬ:\MySymbols contained the symbol for Foo.exe which had a file-name: Foo.pdb. I ran it and installed the symbols in C:\Symbols. Windows Server 2003 with Service Pack 2 x86 retail symbols, all languages (File size: 154 MB - Most customers want this package.) One worked, the other didn't.ĭownloading Windows Server 2003 with Service Pack 2 x86 retail symbols didn't work *** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\kernel32.dll. Defaulted to export symbols for C:\WINDOWS\system32\msvcrt.dll. *** ERROR: Module load completed but symbols could not be loaded for Foo.exe On running the command ld * in WinDbg, I see these errors: 0:000> ld * Defaulted to export symbols for ntdll.dll -įoo.pdb is not present in the same folder where Foo.exe is present. When I open C:\foo\Foo.exe from the 'File > Open Executable' menu, I see this error: *** ERROR: Symbol file could not be found. No symbol path, source path or image path is set Now, I try to debug it using WinDbg.663 X86 Version 5.2. Then, I copied the file Foo.exe to a Windows Server 2003 Enterprise Edition Service Pack 2. I wrote a C++ project called 'Foo' using Microsoft Visual Studio 2005 Verison 7.762 (SP.050727-7600) on Windows XP Professional Version 2002 Service Pack 3.
0 kommentar(er)
