First NetExt custom command added by the community - !wsocket

  • Article

 

James Davis is a big shot in the debugging community and maintains a hard core blog of his experiences. Just soon after NetExt came back online he contacted me via the blog with some very particular questions, the kind of question only seasoned debuggers (and debug extension writers) know how to ask. He focused on writing a custom command for NetExt to list TCP socket details. NetExt comes with a companion netext.tl file with a tree of commands and my support for sockets was just a query in the command tree. To get started with NetExt, check this out: https://blogs.msdn.com/b/rodneyviana/archive/2015/03/10/getting-started-with-netext.aspx

He quickly understood how to make changes in the source code available at codeplex: https://netext.codeplex.com

I may have given him a pointer or two on how to leverage the framework built for NetExt but he mostly got it right from the get go. I was planning to write a few blog entries explaining how to improve NetExt, however he beat me by releasing this amazing post of his experience first: https://www.debugthings.com/2015/03/31/netext-windbg/

This is how the command looks like:

0:011> !wsocket -uniqip ====================================================================================== System.Net.Sockets.Socket``IP Address Summary

IP Address   Count

xxx.xxx.211.196 3