Debugging a running .NET application with WinDbg and an AI agent
Every post in this series so far started from a file: a dump, a gcdump, a trace. That works as long as the answer is in memory at the moment the file is written. Some answers never are. A dump can show that a value is wrong. It cannot show who wrote it, because by the time the dump is taken, the write is long gone. That question needs a debugger attached to the running process, one that stops the process… [read more]