What does it mean when your driver (which you KNOW is loaded, since you are
seeing trace statements from it) does not show up in lm ? At all…
Did you restart the debugger since your driver was loaded?
The debugger has two sources of module list info:
- Notifications from the target.
- .reload.
If you have the debugger running from target boot you’ll have a good
module list from #1. If you restart the debugger after target boot it
will not have #1, so you need to use #2 to get a module list.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of jim
Sent: Thursday, January 19, 2006 12:27 PM
To: Kernel Debugging Interest List
Subject: [windbg] What does it mean when…
What does it mean when your driver (which you KNOW is loaded, since you
are seeing trace statements from it) does not show up in lm ? At all…
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Ya, that seems to do it…
Thanks.
“jim” wrote in message news:xxxxx@windbg…
> What does it mean when your driver (which you KNOW is loaded, since you
> are seeing trace statements from it) does not show up in lm ? At all…
>
>
>