windbg

It is possible to install both x86 and x64 version of WinDbg on the same machine, and if you’re debugging a 32 bit .NET app you should use the x86 version of WinDbg/SOS. The error message is telling you that you’re trying to load the wrong version of SOS for the bitness of the application. … Read more

SRV*C:\dev\symbols*http://msdl.microsoft.com/download/symbols;\\foo\build1234 Should work fine, if \\foo\build1234 is just flat PDB’s. Cache isn’t needed here; you just need to add the directory to your symbol path. The cache keyword specifies where you want to cache your symbol files, and is useful for caching symbols locally from non-indexed shares (like \\foo\build1234) cache*C:\dev\symbols;SRV*C:\dev\symbols*http://msdl.microsoft.com/download/symbols;\\foo\build1234 The above path would store … Read more

Basic Tutorials & Usage Demos Installing and Configuring WinDbg (Windows Debug Tools) Mike Taulty – A word for WinDbg WinDbg Tutorials Windows Debuggers: Part 1: A WinDbg Tutorial Different Ways to “Start”/Attach WinDbg Start Debugging with WinDbg (includes how to debug an .msi) How to debug a Windows service Setting up Windows Debugging Debugging SQL … Read more

Start WinDbg from the command line using the -logo option: windbg.exe -logo logfile.txt That will get everything done logged to the file specified. You can find more details of the command line options here. Or, if you are already in a debugging session, you can use the .logopen command to start logging. For more info … Read more

Actually, Microsoft has now made the Debugging Tools downloadable separately from the SDK. Look for the section “Standalone Debugging Tools for Windows (WinDbg)” about mid-page: for Windows 8.1 for Windows 10