What’s New in CLR 4.5 Debugging API?

Tuesday, April 3, 2012

The most used command in the SOS extension DLL is probably !dumpheap. This command is able to show every object on the managed heap. This capability has no match within Visual Studio. The reason is that Visual Studio uses the CLR debugging API, that doesn’t seem to have this capability. At first glance, the ICorDebugProcess interface has the perfect method: EnumerateObjects. What could be better than that? Unfortunately, the documentation states that this method is not implemented… bummer. A while back I created a project CLR Explorer. This was supposed to be a tool to look at managed processes....

PDC Report: Day 3

Thursday, October 30, 2008

In my previous report, I forgot to mention one more significant product update: Office. The next version of Office (“Office 14”) will have an online version, complete with the famous Ribbon and all major editing capabilities. In addition, synchronization services will allow nice, seamless sync between an online and offline versions, including the ability to open the same file by multiple users for editing with automatic or manual updates. On with day 3! Today’s keynote was by Rick Rashid, the head of Microsoft Research. After some general introduction to his division – MS research is one of...

CLR Explorer v. 0.3

Thursday, September 11, 2008

Another update to my CLR Explorer tool. Changes in this release: A toolbar... Thread call stack includes method signature and values (for the simple types). No generics yet. Can create a dump file on a selected process. If a process crashes, the tool suggests creating a dump file that can be examined later in Visual Studio, WinDbg, etc. Minor bug fixes. CLR Explorer v 0.3
no comments

CLR Explorer Tool

Sunday, August 10, 2008

In the last few days I created the first version of a tool I call "CLR Explorer". This tool allows viewing live CLR-enabled processes, showing the AppDomains, threads and assemblies in those processes. The application is similar in look to Windows Explorer, with a tree-like view on the left and a list view on the right. Here's a screen shot: The tool works by utilizing the native debug interfaces the CLR provides, namely ICorDebug and its derivatives, such as ICorDebugProcess and the like. These are the basis of a CLR based debugger. I have a started an...