phil, Certainly, I have installed OEM tool, but I didn’t load kdex2x86.dll
attached into OEM tool, because it looks too old…
when I install latest windbg, I can find kdex2x86.dll. so I loaded this dll.
if you can login to MS premier online support, see q258793 “How to Find
Memory Leaks by Using Pool Bitmap Analysis”.
ex. you can the following by using !kdex2x86.xpool -map 1
(!kdex2x86.xpool -map 0 is non-paged pool…)
Maximum Number of Pages = 16384 pages
Number of Pages In Use = 16384 pages (100.0%)
+00000 +08000 +10000 +18000 +20000 +28000 +30000 +38000
e1000000: OO{}OOPOOOOOOPOO POOPPPPPPOOOOOOP PPPPPPPPPPPPPPOO
POPPOPPPOOOOOOPP
e1040000: PPPPPPOOOOOOOOOO OOPOOOOOOOOOOOPP OOPOOOPOPPPPOPPP
POPPPPPPPPOPPPOO
e1080000: PPPOOPOOOOO<=–= =–=}OO<=}OOOOOO POOOPPPOOOOPOPO<
<>POOOPPOOOPOP{
e10c0000: }POPOOPOOPPPOOPP POOPOOOPOP{–}PP OOOOO{----------
-----}POOOOOPOPP
e1100000: OOPO{----------- ---------------- -}P{------------
—}PPOPPOOOOPOO
e1140000: OOO<}OPPOOPPO<== >POOPPOOOOPPP<>< >OOOPOOOOOOOOOPO
OOOPOOPOOOOOPOOO
e1180000: OOOOPOOOOOOOOOOO PPOOOPPOP<—}O< >OOOPOOOOOPPOOPO
OPPOOO<}OOPOOOOO
e11c0000: OOOOOOOOOOOOOOOP OOOPO{}OOPOPPOOO OOOOOOOOOOOPOOO{
}OOOOOOPPOPOOPPP
e1200000: {}POPPPPPPPPPPPP PPPPPPPPPPPPPPOP OPPPPPPPOPPPPPPP
PPPPPPPPPPPPPPPP
e1240000: PPPPPPPPPPPPPPOO OPOPOPPPPOPPPPPO O<>OOOOOOOOOOOOO
<=}<------------
.
.
e4d80000: OOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOO OOOOOOOO<>OOOOOO
OOOOOOOOOOOOOOOO
e4dc0000: OOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
e4e00000: OOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOO
e4e40000: OOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOO OOOOOOOOOOOOOO
kimi
-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Saturday, July 14, 2001 1:32 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
How did you find out about xpool? The debugger docs say that kdex2x86.dll
isn’t documented, and have an url to an OEM support tools page,
specifically:
http://support.microsoft.com/support/kb/articles/Q253/0/66.asp
Did you install the OEM support tools and find it that way?
Phil
-----Original Message-----
From: xxxxx@citrix.co.jp [mailto:xxxxx@citrix.co.jp]
Sent: Friday, July 13, 2001 9:24 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
Now windbg works fine.
I didn’t know !pool or !poolfind and !poolused until today. because I am
beginner to debug. 
This is good to look into pool tagging, etc… as you mentioned.
By the way, I am using 3.0.0100, and I think that
kdex2x86.xpool -map is convenience to looking into fragmentations or
contiguous area.
Thank you for all your help
-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Saturday, July 14, 2001 1:07 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
Kimi,
What debugger are you using? I searched the WinDBG docs for xpool, so maybe
it’s an obsolete function, or it’s something under development, that isn’t
ready for use yet?
I use the latest WinDBG beta, and when I want to look at the pool, I use
!pool. If I want to search for a specific tag, I use !poolfind. Will that
give you the information you need?
Phil
-----Original Message-----
From: xxxxx@citrix.co.jp [mailto:xxxxx@citrix.co.jp]
Sent: Friday, July 13, 2001 1:27 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
thank you, Nathan
I could get the information of paged pool at last.
As you mentioned, it took over 10 minutes to get the information, even when
I set baudrate to 115200.
Kimi
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Friday, July 13, 2001 1:23 AM
To: Kernel Debugging Interest List
Cc: xxxxx@citrix.co.jp
Subject: RE: [windbg] RE: kdex2x86.xpool -map 1
I have no idea what !xpool -map does, but if it involves walking a lot
of memory on the target then 15 minutes may be an expected time.
This is because all the data has to come over the COM port which you
probably have set to the default speed. Try boosting the speed to
115200 or 57600 and you will probably see the time reduce to just a
couple of minutes. See the docs on how to change the settings for
non-default baudrates.
-----Original Message-----
From: xxxxx@citrix.co.jp [mailto:xxxxx@citrix.co.jp]
Sent: Thursday, July 12, 2001 4:48 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
I must wait for a lot of time (approx 15 minutes) to get this
information.
Now works fine…
Kimi
-----Original Message-----
From: xxxxx@citrix.co.jp [mailto:xxxxx@citrix.co.jp]
Sent: Thursday, July 12, 2001 5:44 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
Hi I found error when ntoskrnl is loaded. so I created symbol again, and
then I tried this.
Only once time, I can get the correct information, but after that I
can’t
get the information like the following
ntoskrnl!RtlpBreakWithStatusInstruction:
80453d52 cc int 3
kd> !xpool -map
No export xpool found
kd> !kdex2x86.xpool -map 1
Loaded kdex2x86 extension DLL
***** stop here for long time… ******
Must I wait for long time to get the information of paged pool or
nonpaged
pool?
Kimi
-----Original Message-----
From: Ajay K Agrawal [mailto:xxxxx@themoment.com]
Sent: Thursday, July 12, 2001 4:37 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
Where in docs did it give you this impression? I want to make sure
that is
corrected.
In Debugger Extensions | Loading Debugger Extension DLLs
…
There are several methods of loading debugger extension DLLs, as well as
controlling the default debugger extension DLL and the default debugger
extension path:
(Before starting the debugger) Use the _NT_DEBUGGER_EXTENSION_PATH
environment variable to set the default path for extension DLLs. This
can be
a number of directory paths, separated by semicolons.
…
It wasn’t clear that windbg would load the extensions shipped with it.
Thanks!
-Ajay
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Wednesday, July 11, 2001 12:11 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
It is meant to be used if you have an extension DLL of your own that you
want the debugger to grab from some location. It is not required for
using the extenstions that shipped with the debugger.
I recommend against doing this since it will make it easy to get the
wrong path in there.
Where in docs did it give you this impression? I want to make sure that
is corrected.
Thanks.
-----Original Message-----
From: Ajay K Agrawal [mailto:xxxxx@themoment.com]
Sent: Wednesday, July 11, 2001 11:22 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: kdex2x86.xpool -map 1
Why are you doing Step 2? If you are debugging w2kchk then this path
is
automated added by the debugger.
Is this also true of w2kfre. For example the following as a system
variable.
_NT_DEBUGGER_EXTENSION_PATH=C:\Program Files\Debugging Tools for
Windows\w2kfre
I got the impression from Windbg help manual that this is required.
-Ajay
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Wednesday, July 11, 2001 11:04 AM
To: Kernel Debugging Interest List
Cc: Kernel Debugging Interest List; Windbg External Feedback
Subject: [windbg] RE: kdex2x86.xpool -map 1
Adding xxxxx@microsoft.com which is a direct line to the debugger
team.
Why are you doing Step 2? If you are debugging w2kchk then this path is
automated added by the debugger. If you aren’t debugging w2kchk then
you are using an incompatible version of the extension dll.
What version of the debugger are you using?
What OS is that target? What SPs are installed?
Are symbols loading correctly for ntoskrnl?
-----Original Message-----
From: xxxxx@citrix.co.jp [mailto:xxxxx@citrix.co.jp]
Sent: Wednesday, July 11, 2001 10:16 AM
To: Kernel Debugging Interest List
Subject: [windbg] kdex2x86.xpool -map 1
Hello
I do the following steps to dump information about managed pool blocks
in
the system.
but I got the error, “InternalGlobalPool error” in the debugger. I don’t
know detailed error message because I am in my house…
- set the following key using gflags.exe
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager]
“GlobalFlag”=dword:00000c00
- reboot target machine
- set _NT_DEBUGGER_EXTENSION_PATH=C:\Program Files\Microsoft Debugging
Tools\w2kchk
- !load kdex2x86.dll
- !kdex2x86.xpool -map 1
- I got error “InternalGlobalPool error”
Any suggestion?
Kimi
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@themoment.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@themoment.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@citrix.co.jp
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@citrix.co.jp
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@citrix.co.jp
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@citrix.co.jp
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com