Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.More Info on Driver Writing and Debugging
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Debug output markup
Jamey_Kirby
Member - All Emails Posts: 459
It's probably about time to consider using a markup language like HTML in WinDbg output. I use the kernel debugger mostly for instrumentation, and it would be cool if there was an instrumentation mode where marked up output would be displayed in a new type of WinDbg output window; separate from the normal output window.
Howdy, Stranger!
| Upcoming OSR Seminars | ||
|---|---|---|
| OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
| Kernel Debugging | 30 January 2023 | Live, Online |
| Developing Minifilters | 20 March 2023 | Live, Online |
| Internals & Software Drivers | 17 April 2023 | Live, Online |
| Writing WDF Drivers | 22 May 2023 | Live, Online |
Comments
> It's probably about time to consider using a markup language like HTML in WinDbg output. I use the kernel debugger mostly for instrumentation, and it would be cool if there was an instrumentation mode where marked up output would be displayed in a new type of WinDbg output window; separate from the normal output window.
Show me an example of a what it would look like if you had your wish,
because I can't visualize it. WinDbg already supports a limited amount
markup; that's how you can put clickable links into your debug output to
suggest followup commands.
In my mind, however, I cannot imagine wasting time trying to embed red,
flashing, bold text, paragraph alignment markers, and spinning logo
images into my debug output. The goal, after all, is to debug code, not
to produce quality desktop publishing.
Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.
windbg already supports DML, the "debugger markup language". But I guess you want something a lot richer than just making text bold and italic.
!ndiskd.netreport is some effort in that direction, although it was a ton of work to put that together, and I doubt that most debugger extensions would go through the trouble. If you want to build a beautiful report using a language like HTML, then I suggest you just use HTML like ndiskd did.
But instead of expecting each debugger extension to build a beautiful reporting GUI, the debugger team is trying to get extensions to expose their innards directly into the "debugger data model". This establishes a separation between data & view. Presumably, then, the next phase of their master plan is building rich and awesome views, once all this great data is available.
But the conversion to "debugger data model" does seem to be going slowly, because spending time tinkering with a debugger extension is, realistically speaking, the last thing on everyone's todo list.
http://kdext.com/extensions/uienh_mchl.html