Debugging Tools for Windows: Symbol proxy is not a proxy
I am trying to create a symbol proxy using symproxy.dll from Windows Debug Tools. When I issue ".reload / f" from the debugger, none of the symbol files can be found. It looks like Symproxy is not going to the Symbol Server to actually get the symbols. For example, I can't see anything in Wireshark.
SYMPROXY.DLL is definitely loading - I can see some entries in the event log and http: // my-server / symbols / status returns the correct kind of information.
As far as I can tell from the documentation in the docs. Why is symproxy not submitting to Microsoft site? What am I doing wrong? I need this to work because the machine I'm debugging on doesn't have external access.
The field that symproxy is running on has internet access - I regularly use it for debugging. The symbol path configured in the registry for symproxy looks correct. It doesn't need to go through a proxy to connect to the internet and I've configured it in the registry as well.
When I use! sym noisy in another field, it binds to symproxy but just says "file not found". This is similar to symproxy, just serves for content, not browsing MS symbol servers as intended.
source to share
You have several options available to you:
- Make sure you are going against the Microsoft symbol server using the .symfix (or .symfix +) commands. The "+" version stores all your other symbol paths and just adds the official MS symbol server to your list.
- Try typing "! Sym noisy" before your reboot command. This will instruct WinDbg to show you exactly how it resolves your symbols, as well as what errors it encounters along the way (no PDBs, cannot communicate with a remote server, etc.).
source to share
first, you have the correct symbol server: http://msdl.microsoft.com/download/symbols
Second, does your proxy server have access to the internet? and is it configured to allow symproxy access? Maybe symproxy isn't proxying itself (check symhttp.doc in the debug tools directory).
I would try a few steps to debug the debugger - you can run windbg with a crash dump in the proxy window if you can copy the symbols manually into the debugger box. If not, you need to allow internet access.
source to share