Dump and analyze .Net applications memory ( a gui for WinDbg and ClrMd )
-
Updated
Jun 25, 2020 - C#
#
clrmd
Here are 13 public repositories matching this topic...
Host of debugging-related extensions such as post-mortem tools or WinDBG extensions
-
Updated
Nov 27, 2021 - C#
Utility to resolve SQL Server callstacks to their correct symbolic form using just PDBs and without a dump file
debugging
stack
dll
frames
pdb
internals
performance-analysis
windbg
callstack
sqlserver
troubleshooting
hacktoberfest
clrmd
sqlserver-2017
xevents
sql-releases
sqlserver-2019
pdbs
msdia140
diasdk
-
Updated
Apr 20, 2022
Examine, create and interact with remote objects in other .NET processes.
debugging
csharp
dotnet
reverse-engineering
instrumentation
forensics
clrmd
dynamic-debug
forensics-tools
-
Updated
Apr 9, 2022 - C#
A simple tool that helps you run common diagnostics steps instead of battling with WinDbg.
-
Updated
Aug 22, 2019 - C#
C# programming written entirely in VisualStudio/Windows.
visual-studio
csharp
dll
powershell
clrmd
net-framework
exchange-server
windows-presentation-foundation
windows-workflow
reviews-appreciated
workflow-activities
-
Updated
Mar 20, 2019 - C#
-
Updated
Sep 2, 2019 - C#
A little graphical user interface to find memory leaks in the .net managed heap based on microsofts https://github.com/Microsoft/clrmd.
-
Updated
Oct 8, 2019 - C#
Diagnostics utility to analyze memory dumps of a .NET application
-
Updated
Jan 24, 2022 - C#
Improve this page
Add a description, image, and links to the clrmd topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the clrmd topic, visit your repo's landing page and select "manage topics."
It would be useful if this information (boxed in red) were able to be copy and pasted:
4,086,800 strings, 630,116 unique. 468,564,642 total string bytes, of which 342,442,924 (73.1%) are wasted on duplicates (12.6% of 2,708,496,737 managed heap bytes).
For now I am working around