I’m attempting to set up a symbol proxy using symproxy.dll from Debugging Tools for Windows. When I issue ‘.reload /f’ from the debugger, none of the symbol files can be found. It looks like Symproxy isn’t going out to the Microsoft Symbol Server to actually get the symbols. I see nothing in Wireshark, for example.
SYMPROXY.DLL is definitely being loaded — I can see some entries in the Event Log, and http://my-server/symbols/status returns valid-looking information.
I’ve followed the instructions in the documentation as far as I can tell. Why won’t symproxy go to Microsoft’s site? What am I doing wrong? I need this to work, because the machine on which I’m debugging doesn’t have external access.
The box on which symproxy is running has Internet access — I regularly use it for debugging. The symbol path configured in the registry for symproxy looks correct. It doesn’t have to go through a proxy to get to the Internet, and I’ve configured that in the registry as well.
When I use !sym noisy on the other box, it contacts symproxy, but simply says ‘file not found’. It’s like the symproxy is simply serving the content, rather than doing a lookaside to the MS symbol servers, like it’s supposed to.
In the meantime, I’ve installed and configured Squid on the shared machine. This seems to work. I’d have preferred to use symproxy, but I just don’t have time to dig into why it’s not working.