I’m working on a debugger extension, whose main purpose is to read /
interpret / display the state of device drivers that my company is
implementing. What is the easiest way to find instances of my driver’s
device objects from a debugger extension?
I could alter the driver to make finding the device instances easier, but I
want to avoid altering the device driver code as much as possible.
Basically, I want an API that provides what !drvobj does.
– arlie
The debugger person at Microsoft who can best answer this is out until
February. If you don’t get a different reply before then I’ll get him
to chime in.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Thursday, January 26, 2006 2:36 PM
To: Kernel Debugging Interest List
Subject: [windbg] Finding instances of DEVICE_OBJECT from debugger
extensions
I’m working on a debugger extension, whose main purpose is to read /
interpret / display the state of device drivers that my company is
implementing. What is the easiest way to find instances of my driver’s
device objects from a debugger extension?
I could alter the driver to make finding the device instances easier,
but I want to avoid altering the device driver code as much as possible.
Basically, I want an API that provides what !drvobj does.
– arlie
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
Hi,
Pass in the address of your driver object (!object \driver\xxx), from there
you can get the first device object from DriverObj->DeviceObject, then you
can get all of the other device objects through DeviceObject->NextDevice.
If you also want to automate the finding of the driver object then I believe
you have serious work to do (I’ve managed to make it work in the past but it
ended up not really being worth the effort)
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Arlie Davis” wrote in message
news:xxxxx@windbg…
> I’m working on a debugger extension, whose main purpose is to read /
> interpret / display the state of device drivers that my company is
> implementing. What is the easiest way to find instances of my driver’s
> device objects from a debugger extension?
>
> I could alter the driver to make finding the device instances easier, but
> I
> want to avoid altering the device driver code as much as possible.
> Basically, I want an API that provides what !drvobj does.
>
> – arlie
>
>
>
>
> -----Original Message-----
If you also want to automate the finding of the driver object then I
believe
you have serious work to do (I’ve managed to make it work in the past
but
it
ended up not really being worth the effort)-scott
[CG]
Walk the object tree. I’ve done that in an kdext and it was fun:)
–
Calvin Guan (Windows DDK MVP)
NetXtreme Longhorn Miniport Prime
Broadcom Corp. www.broadcom.com
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com