Windbg Series
This series discusses about different ways in which Windbg can be used along with .NET for diagnosing and troubleshooting.
NOTE: This series is a work in progress. Please check back regularly for updates.
-
Identify and Patch .NET Code using Windbg
-
Conditional Breakpoint in .NET using Windbg
-
Function hit count using Pseudo-Register in Windbg
-
Identifying High CPU in GC (.NET) because of LOH – using Windbg
-
Get function return values and profiling information in .NET using Windbg
-
Exploring undocumented SOS function in Windbg – .NET 4.0
-
Debugging trick for .NET Windows Service
-
Using windbg as a Sql profiler in .NET
-
Debugging unknown termination of adplusmanager.exe – Windbg
-
Debugging .Net framework source code within Windbg
-
Undocumented PSSCOR2 functions
-
Using a native Dll via LoadLibrary within ASP.NET runtime
-
Case of NullReferenceException not handled by sos / windbg
-
Debugging .NET – mystery between DEBUG versus RELEASE within windbg
-
Debugging Generic System.Nullable within Windbg
-
Recursive !dumpmt – Windbg
-
dumpstring – windbg
-
Custom DumpArray – Windbg
-
Do I have Managed or Native memory leak?
-
Debugging base class method with conditional break point in .NET using Windbg
-
Using Windows Error Reporting (WER) API in managed code to generate memory dump
-
Using Mono Cecil Decompiler within Windbg to decompile
-
Debugging .Net Framework 4.0 without source code using windbg
-
Remote Debugging with Windbg and Powershell Remoting
-
.NET – How can debug=true extend the life time of local variable
-
Exploring SOSEX and Windbg to debug .NET 4.0
-
Script to load sos within Windbg based on .NET Framework version