symbol server support (MS symbols...)

[x13pixels]

[direbroom]

[sonictk]

I know this has already been assigned a priority and ticketed, but I'd like to make a pre-implementation suggestion: one of the most annoying things about the current way symbol servers work in VS/WinDbg is that you either have to use the Visual Studio GUI to set your servers individually in it and WinDbg, or use the _NT_SYMBOL_PATH environment variable but lose the ability to quickly configure which servers to use and/or load. It's especially annoying when debugging 3rd-party applications which you obviously don't have the symbols for, but Visual Studio will keep attempting to search for symbols regardless. One of the "nice" things about remedybg for me is that since it actually doesn't have support for symbol servers at the moment, attaching to such 3rd-party applications is blazingly fast and I only load the symbols for my own DLLs. It'd be nice to keep this in mind whenever this feature is ultimately implemented, to allow for quickly customizing which symbol server locations to load/search from, or whether to load any symbols at all except for ones local on the machine, while still respecting updates from _NT_SYMBOL_PATH.

Hopefully that makes sense and is a desirable goal for others as well.

[Manuzor]

Loading symbols lazily/on-demand should keep startup times low. Or doing loads from symbol servers or file shares in the asynchronously in the background.