More Suggestions for Experimenting with WinDbg


The walkthrough examples in this chapter show only the basics of what you can do with WinDbg. Some further things to try:

  • Step through more of the code.

    Examine the values of the variables and see what the various UMDF or KMDF routines do.

  • Set a breakpoint in the driver's read, write, or device I/O control callbacks and use the test application to read or write a value or to send a device I/O control request.

    These callbacks manipulate WDF memory objects that contain the related data buffers.

  • Run the other WDF debugger extensions to see what kind of information they return. In particular, run !driverinfo, which displays useful information about the driver.

    Be sure to run any command strings that are included in the output.

     Tip  See "Specialized Extensions" in the Windows Debugging Tools help file for reference documentation for the WDF debugger extensions.

  • Read the debugging documentation.

    There's much more to driver debugging than can be covered here.

  • Monitor a driver-oriented newsgroup or e-mail list.

    Debugging issues are a common topic, and you can see how the experts handle such problems.




Developing Drivers with the Microsoft Windows Driver Foundation
Developing Drivers with the Windows Driver Foundation (Pro Developer)
ISBN: 0735623740
EAN: 2147483647
Year: 2007
Pages: 224

Similar book on Amazon
Windows Internals, Part 1: Covering Windows Server 2008 R2 and Windows 7
Windows Internals, Part 1: Covering Windows Server 2008 R2 and Windows 7
Windowsu00ae Internals: Including Windows Server 2008 and Windows Vista, Fifth Edition (Pro Developer)
Windowsu00ae Internals: Including Windows Server 2008 and Windows Vista, Fifth Edition (Pro Developer)
Advanced Windows Debugging
Advanced Windows Debugging
The Windows 2000 Device Driver Book: A Guide for Programmers (2nd Edition)
The Windows 2000 Device Driver Book: A Guide for Programmers (2nd Edition)

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net