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.

  1. Identify and Patch .NET Code using Windbg

  2. Conditional Breakpoint in .NET using Windbg

  3. Function hit count using Pseudo-Register in Windbg

  4. Identifying High CPU in GC (.NET) because of LOH – using Windbg

  5. Get function return values and profiling information in .NET using Windbg

  6. Exploring undocumented SOS function in Windbg – .NET 4.0

  7. Debugging trick for .NET Windows Service

  8. Using windbg as a Sql profiler in .NET

  9. Debugging unknown termination of adplusmanager.exe – Windbg

  10. Debugging .Net framework source code within Windbg

  11. Undocumented PSSCOR2 functions

  12. Using a native Dll via LoadLibrary within ASP.NET runtime

  13. Case of NullReferenceException not handled by sos / windbg

  14. Debugging .NET – mystery between DEBUG versus RELEASE within windbg

  15. Debugging Generic System.Nullable within Windbg

  16. Recursive !dumpmt – Windbg

  17. dumpstring – windbg

  18. Custom DumpArray – Windbg

  19. Do I have Managed or Native memory leak?

  20. Debugging base class method with conditional break point in .NET using Windbg

  21. Using Windows Error Reporting (WER) API in managed code to generate memory dump

  22. Using Mono Cecil Decompiler within Windbg to decompile

  23. Debugging .Net Framework 4.0 without source code using windbg

  24. Remote Debugging with Windbg and Powershell Remoting

  25. .NET – How can debug=true extend the life time of local variable

  26. Exploring SOSEX and Windbg to debug .NET 4.0

  27. Script to load sos within Windbg based on .NET Framework version



 

Leave a Reply

Your email address will not be published. Required fields are marked *