-
The CLRMD works great. As it shows the class instances stored in heap and we can able to get the instance count as well as size of each instance occupied in heap.
It would be better if we can try to …
-
In the DacLibrary finalizer, we FreeLibrary the DAC. Unfortunately, sometimes some IXCLR\* RCWs can live past this point, and then when the process is shutting down and the CLR is trying to call Relea…
-
From some experimentation with parallelizing various heap traversal algorithms, I'm hitting odd exceptions that are only happening in multi-threaded usage of the same `ClrHeap`. To be clear, I am usin…
-
Attaching to a process with more than 4GB heap works great. Opening a dump file from that process fails with the following exception:
```
ClrDiagnosticsException: Failure loading DAC: CreateDacInstan…
-
Extend ClrHeap API and provide with method to get ClrType by MT& CMT pair, without need in object address.
That will allow to store information about types and later re-use it after app restart.
Thi…
-
How do we use the IDebugControl interface to wait for events?
```
IDebugControl control = (IDebugControl)dataTarget.DebuggerInterface;
var hr = control.SetExec…
-
Hi,
I'm using the debug engine interop interfaces (as well as CLRMD) and some methods accept IntPtr instead of the "proper" interface (e.g. IDebugClient.SetEventCallbacks). I've tried to replace the …
-
ClrMD library exposes public interface and all the platform specific classes are marked as `Internal`. For instance, currently you cannot:
- get MethodTable for type;
- get MethodDescriptor for meth…
-
Currently, there's nothing that we can do with a .NET dump unless it has the full process memory. But it's possible (and some attempts were made in the past, e.g. [ClrDump](http://blogs.msmvps.com/deb…
-
The public version of CLRMD doesn't support >4GB dump files because of issues in the `DumpReader` class (see [this issue](https://github.com/Microsoft/dotnetsamples/issues/24)).