Scott,
I just discovered that if I bring up Windbg and NOT do a .reload, I run into the same problem with !devnode 0 1. After I do the .reload, !devnode 0 1 works ok.
Thanks,
Howard
-----Original Message-----
From: Howard Keller
Sent: Monday, February 23, 2004 8:03 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] using !devnode 0 1
Hi Scott,
I believe Windbg is properly set up for using the symbol server.
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\work\Sensormatic\sw\test\pcitest\Debug;C:\work\Sensormatic\sw\src\objchk_wnet_x86\i386
Let me show you a strange sequence that just occured:
kd> !devnode 0
Error retrieving address of IopRootDeviceNode
kd> !symbol noisy
No export symbol found
kd> .reload
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
…
Loading unloaded module list
…
Loading User Symbols
*** ERROR: Module load completed but symbols could not be loaded for sym_u3.sys
*** ERROR: Module load completed but symbols could not be loaded for e100bnt5.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dump_diskdump.sys -
*** ERROR: Module load completed but symbols could not be loaded for dump_sym_u3.sys
kd> !devnode 0 1
Dumping IopRootDeviceNode (= 0x85e6d368)
DevNode 0x85e6d368 for PDO 0x85e6d460
Parent 0000000000 Sibling 0000000000 Child 0x85e48f28
InstancePath is “HTREE\ROOT\0”
Flags (0x00040459) DNF_MADEUP, DNF_PROCESSED,
DNF_ENUMERATED, DNF_ADDED,
DNF_NO_RESOURCE_REQUIRED, DNF_STARTED
DisableableDepends = 9 (from children)
ETC…
Why would it just suddenly start to work on the reload??
Thanks,
Howard
-----Original Message-----
From: Scott Noone [mailto:xxxxx@osr.com]
Sent: Friday, February 20, 2004 2:23 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] using !devnode 0 1
Are you using the Microsoft symbol server? It should handle getting all
the right symbols loaded for you. If not, follow the directions here and see
if it fixes your problems:
http://www.microsoft.com/whdc/ddk/debugging/symbols.mspx
If you’re already using the symbol server, then you can try doing a
!sym noisy
.reload
This should give you some insight into why WinDBG isn’t properly loading
symbols.
Regards,
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Howard Keller” wrote in message
news:xxxxx@windbg…
Hi Scott,
No, I’m not sure I have the symbols set up properly. I see a number of
errors trying to load symbols when I run. Not everything reports an error.
What would you recommend I verify to make sure things are properly set up?
Thanks,
Howard
-----Original Message-----
From: Scott Noone [mailto:xxxxx@osr.com]
Sent: Friday, February 20, 2004 11:08 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] using !devnode 0 1
Hi,
Sounds like a symbols problem to me. Are you sure they’re setup
correctly?
Regards,
-scott
–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com
“hkeller” wrote in message
news:xxxxx@windbg…
> Hi all,
>
> I’m getting an error in Windbg trying to do an !devnode 0 1. Windbg is
> reporting
> “Error retrieving address of IopRootDeviceNode”
>
> I’m on win2ksp3 checked build and the version of Windbg I’m using is
> 6.2.0013.1. I also find a bunch of other extended commands don’t work,
> possibly due to the same problem. Any ideas?
>
> Thanks,
>
> Howard Keller
>
>
>
—
You are currently subscribed to windbg as: xxxxx@memecdesign.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@memecdesign.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@memecdesign.com
To unsubscribe send a blank email to xxxxx@lists.osr.com