This repository contains hands-on excercises for WinDBG related workshops (both about memory management and scenarios for high CPU usage, deadlocks and other threading issues)
Eeach excercise is a small application that simulates a particular issue, which can be then investigated using a memory dump and WinDBG.
In order to try the excercises, you should do ensure your development workstation is ready for dump investigation. The assumption is that the dev machine runs Windows 10.
Note: it is possible to investigate memory dumps on Linux/MacOS as well - the principle is the same yet the tools will be different
For DotNext workshop "Crashes, hangs, and high CPU", we will use excercises found in the "High CPU and Threads" folder of the solution. Note that each excercise contains hints.md, which contains hints on how the case can be investigated and solution.md which contains the commands needed to investigate the issue (with explanations as well :))
- Make sure you have .Net 4.8 developer pack and .Net 5.0 SDK are installed (https://dotnet.microsoft.com/download/visual-studio-sdks)
- Ensure you have Visual Studio 2019 or any IDE capable of compiling and running .Net 5.0
- Install WinDbg Preview from Windows Store.
- WinDbg requires a bit of configuring. Take a look at the following or use this blog post as a guide
Set up symbol resolution string. The format of the symbol string is cache[local cache folder 1][local cache folder 2];srv[local cache folder]*[symbol server path]*
Note 1: This will enable WinDbg to resolve symbols so proper stack traces can be displayed.
Note 2: !sym noisy on command will enable debug output to see what kind of symbols WinDbg looks for and why the resolution is missing.
- Download Process Explorer from here. It will be useful for taking dumps of processes.
- Download and install Windows 10 SDK (you can download it from here). Make sure to tick Debugging Tools for Windows when you install
- Download ProcDump from here
