Unable to retrieve the PEB address.

OSR_Community_User · November 8, 2000, 2:12pm

Hi All,

I’m using Windbg 1.0.0006.0 for kernel driver
debugging.

Following is the debugging setup;
Host : Win 2k professional only (build 2195).
Target: Win 2k Server only (build 2195).

I have a problem. After the target hits DbgBreakpoint
in my Driver Entry it starts loading symblos of the
loaded modules and some times it pops up a message on
command prompt saying…

Loading unloaded module list
Unable to examine unloaded module list
Unable to retrieve the PEB address. This is usually
caused by being in the wrong process context or by
paging

Whats happening above ? Whats that PEB address ? How
can I Avoid this message ?

This happens only when I put a DbgBreakPoint in driver
entry and when the targets breaks I get above message.

Any help ?
Thanks in Anticipation.
Girish

Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one Place.
http://shopping.yahoo.com/

OSR_Community_User-48 · November 8, 2000, 2:22pm

All this message really says is that it doesn’t know what modules are
loaded for the current process. This is usually because the data for
the process is paged out. The cause of this is that you can’t load
symbols for the UM process who’s context you are in.

If you are debugging a driver, then you probably don’t care & this does
not affect you. If you want to debug a UM process, then it is prefered
to use a UM debugger on the target machine.

-----Original Message-----
From: Girish Kumar B K [mailto:xxxxx@yahoo.com]
Sent: Wednesday, November 08, 2000 11:08 AM
To: Kernel Debugging Interest List
Subject: [windbg] Unable to retrieve the PEB address.