Microsoft public symbol server
The Microsoft symbol server makes Windows debugger symbols publicly available.
You can refer directly to the public symbol server in your symbol path in the following manner:
DownstreamStore must specify a directory on your local computer or network that will be used to cache symbols. This downstream store holds symbols that the debugger has accessed; the vast majority of symbols that have never been accessed remain on the symbol store at Microsoft. This keeps your downstream store relatively small and allows the symbol server to work quickly, only downloading each file once.
To avoid typing this long symbol path, use the .symfix (Set Symbol Store Path) command. The following command appends the public symbol store to your existing symbol path:
If local symbol cache location is omitted, the sym subdirectory of the debugger installation directory will be used.
Use the .sympath (Set Symbol Store Path) command to display the full symbol path. This example shows how to use symfix to create a local symbol cache and use the Microsoft http symbol server.
0: kd> .symfix c:\MyCache 0: kd> .sympath Symbol search path is: srv* Expanded Symbol search path is: cache*c:\MyCache;SRV*https://msdl.microsoft.com/download/symbols
For more information about working with symbols, see the Symbol path for Windows debuggers.
Symbol File Compression
The Microsoft Symbol Server provides compressed versions of the symbol files. The files have an underscore at the end of the filename’s extension to indicate that they are compressed. For example, the PDB for ntdll.dll is available as ntdll.pd_. When SymProxy downloads a compressed file, it will store the file decompressed in the local file system. The DontUncompress registry key can be set to disable this behavior in SymProxy.
Refer to the Debugger topic SymStore for information on using SymStore.exe /compress to store your own symbols compressed on your symbol server.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.