Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

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/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

[WinDbg] Catch-22

OSR_Community_UserOSR_Community_User Member Posts: 110,217
The following is a quote from the WinDbg home page:

"This Beta of Debugging Tools for Windows contains many bug fixes and new
enhancements. The debuggers are stable and more reliable than Version
2.0.23.0 and we recommend that you upgrade your debuggers to this new
version. It is also a requirement to use this Beta of the Debugging Tools
for Windows if you wish to debug post Beta 2 versions of Windows XP."

Well, boys and girls, I'm here to tell you that that is an impossible thing
to do. At least it is with 2469. None of the bang commands work with the XP
2469 retail symbols. That leaves you the ability to reboot, and set
breakpoints. You cannot dump the stack ... !stack doesn't work. Why? Because
I'm using the wrong symbol set. But I downloaded the support ISO file dated
23 May 01, and then I installed the retail symbols. (and they did install
this time.)

You cannot look at IRPs ... !irpfind and !irp are non-functional. The same
for !drvobj and !devobj. Every !bang command I have tried puts up the same
bitch box:

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** ***
*************************************************************************

Could I please make a suggestion? Try it yourself before you post it. Or
contact one of us poor dumb schmucks that are willing to test this stuff for
you and have us test it till you get it right. This makes the 3rd or 4th
drop that has the same problems --- The symbols are screwed.

Consider yourself contacted.


Gary G. Little
Staff Engineer
Broadband Storage, Inc.
[email protected]
[email protected]



---
You are currently subscribed to windbg as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-windbg-$subst('Recip.MemberIDChar')@lists.osr.com
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

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!
Writing WDF Drivers 24 January 2022 Live, Online
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online