Hello NTDebuggers, I’d like to announce something new for our community to share. We have decided to host an Open Source Debugger Extension project called ODbgExt on codeplex.com Right now it’s just the basic framework. This will be something we can work on together as a community. Think of it as a debugger extension by the people for the people. Jason Epperly and I (Jeff Dailey) will be the project managers for the codeplex environment. You can find the project on http://www.codeplex.com/ODbgExt
ODbgExt is an open source debugger extension for WinDbg that is intended to be developed by the debugging community. It is based on the Windows Debugger SDK Sample ‘exts’ and uses the COM Debugger interface IDebugControl. The primary objective of the project is to provide the debugging community a central location to share their debugger extensions that help to isolate common problems in the community and make debugging both live systems and dumps easier. The initial release will be the basic framework that we expect other developers to contribute to. There will be very basic functionality in the initial version. We, GES (Global Escalation Services) intend on doing a series of blogs to talk about writing debugger extensions over the coming year. As we blog about writing extension we will include the code in ODbgExt (This project). This is the same group that runs the http://blogs.msdn.com/ntdebugging blog. We encourage you to sign up and contribute your debugger extension ideas and or code to the project. Simply create a codeplex account and request access.
Things we would like to include:
• A Graphical representation of Kernel, and User mode execution time by process and thread, while correlating to idle / non-idle time
• A Graphical representation of idle time for kernel and user mode.
• A Graphical representation of pool resources used on a per process bases along with handle table counts.
• Hang detection, scanning for various conditions that could cause hangs in a system or user mode process.
• Detailed system information such as oldest and newest binaries.
• Binary info based on vendor name
• A better dissembler that colorizes calls, jumps and indents to show code flow
• Extensive use of DML (Debugger Mark-up Language) to enable more point and click debugging within windbg.
• Support for a SQL Database backend to allow storing information about debugging sessions or binaries in a SQL Database.
• Warnings when critical thresholds are exceeded such as handle counts over 10,000, Low PTE Conditions, etc.
• Simplified searching for pool tags in binaries.
• Support for VBA for Windbg
• Dump annotation, via dump streaming; the ability to embed data into a dump via the debugger extension and later retrieve it. (Imagine embedded debug notes)
• Embedding a snapshot of performance data in the dump at the time the dump is taken, ie. CPU, IO etc.
We hope you are as excited about this project as we are! Please feel free to suggest more ideas for this project and by all means feel free to sign up and contribute some code!
Platforms Global Escalation Services