Comments on: Writing the WinDbg Extension to Enable Writing WinDbg Extensions in Managed Code http://dotnetdebug.net/2005/11/07/writing-the-windbg-extension-to-enable-writing-windbg-extensions-in-managed-code/ Because sometimes you need to dig deep! Wed, 29 May 2013 11:33:00 +0000 hourly 1 http://wordpress.org/?v= By: Eran Sandler http://dotnetdebug.net/2005/11/07/writing-the-windbg-extension-to-enable-writing-windbg-extensions-in-managed-code/comment-page-1/#comment-91582 Eran Sandler Tue, 26 Oct 2010 17:54:32 +0000 #comment-91582 I had something very basic working but never had time to finish it and it eventually didn’t happen. I hope someone else picked (or will pick) the glove.

]]> By: Ikas http://dotnetdebug.net/2005/11/07/writing-the-windbg-extension-to-enable-writing-windbg-extensions-in-managed-code/comment-page-1/#comment-91576 Ikas Tue, 26 Oct 2010 17:16:40 +0000 #comment-91576 Did this ever come out successfully ?
Anything on the 5th anniversary since this was published ?

]]> By: Dan McKinley http://dotnetdebug.net/2005/11/07/writing-the-windbg-extension-to-enable-writing-windbg-extensions-in-managed-code/comment-page-1/#comment-55 Dan McKinley Mon, 07 Nov 2005 18:47:00 +0000 #comment-55 How do you plan on publishing the extensions that people write, given that extension commands are implemented as exported dll functions? I guess all of the managed commands will have to go through the same stub !command?

Also, one thing that would definitely be useful would be managed code that takes advantage of SOS commands. Parsing the output of !do and providing a managed API for looking at objects would go a long way towards usability.

My thinking there is that it’s a little difficult to write something useful for managed code here unless you’re willing to dig through the SSCLI and get a feel for CLR internals. I’m willing to do that, as I imagine you are, but the vast majority of people are not.

Anyway, if you want to put this project on sourceforge or gotdotnet I’d be willing to contribute.

]]>