I am using version 6.12 of windbg. I am sure that in the past the !poolused
command displayed the current allocations for each tag. I am looking at a
dump and it looks like the display is a total of all allocations, not the
current ones. For example, the non paged usage for AFdp is 4266791656. This
has to be a running total which makes it pretty useless.
Bill Wandel
It should be showing the current number of allocations and bytes, not a
running total. You can use !poolused 1 for the breakdown, which will show
total allocs and total frees.
-scott
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Bill Wandel” wrote in message news:xxxxx@windbg…
I am using version 6.12 of windbg. I am sure that in the past the !poolused
command displayed the current allocations for each tag. I am looking at a
dump and it looks like the display is a total of all allocations, not the
current ones. For example, the non paged usage for AFdp is 4266791656. This
has to be a running total which makes it pretty useless.
Bill Wandel
That is what is supposed to show but it isn’t. The dump is a truncated full
dump so maybe that is the problem.
For some reason, customers insist on full dumps when in most cases just
kernel dumps is all that is needed.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Tuesday, November 16, 2010 1:44 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] poolused
It should be showing the current number of allocations and bytes, not a
running total. You can use !poolused 1 for the breakdown, which will show
total allocs and total frees.
-scott
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Bill Wandel” wrote in message news:xxxxx@windbg…
I am using version 6.12 of windbg. I am sure that in the past the !poolused
command displayed the current allocations for each tag. I am looking at a
dump and it looks like the display is a total of all allocations, not the
current ones. For example, the non paged usage for AFdp is 4266791656. This
has to be a running total which makes it pretty useless.
Bill Wandel
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
!!poolused reads usage counters from a set of per-processor tables. For a particular tag, only the total allocated size across all tables makes sense. If one or more tables could not be read due to missing data in the dump, allocation sizes and/or counts can become negative, which is probably what happened with the tag below.
Thanks,
Pavel
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Bill Wandel
Sent: Tuesday, November 16, 2010 11:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] poolused
That is what is supposed to show but it isn’t. The dump is a truncated full dump so maybe that is the problem.
For some reason, customers insist on full dumps when in most cases just kernel dumps is all that is needed.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Tuesday, November 16, 2010 1:44 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] poolused
It should be showing the current number of allocations and bytes, not a running total. You can use !poolused 1 for the breakdown, which will show total allocs and total frees.
-scott
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Bill Wandel” wrote in message news:xxxxx@windbg…
I am using version 6.12 of windbg. I am sure that in the past the !poolused command displayed the current allocations for each tag. I am looking at a dump and it looks like the display is a total of all allocations, not the current ones. For example, the non paged usage for AFdp is 4266791656. This has to be a running total which makes it pretty useless.
Bill Wandel
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Thanks. This particular dump also has negative counts in the poolused
output.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pavel Lebedynskiy
Sent: Tuesday, November 16, 2010 2:48 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] poolused
!!poolused reads usage counters from a set of per-processor tables. For a
particular tag, only the total allocated size across all tables makes sense.
If one or more tables could not be read due to missing data in the dump,
allocation sizes and/or counts can become negative, which is probably what
happened with the tag below.
Thanks,
Pavel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bill Wandel
Sent: Tuesday, November 16, 2010 11:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] poolused
That is what is supposed to show but it isn’t. The dump is a truncated full
dump so maybe that is the problem.
For some reason, customers insist on full dumps when in most cases just
kernel dumps is all that is needed.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Tuesday, November 16, 2010 1:44 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] poolused
It should be showing the current number of allocations and bytes, not a
running total. You can use !poolused 1 for the breakdown, which will show
total allocs and total frees.
-scott
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Bill Wandel” wrote in message news:xxxxx@windbg…
I am using version 6.12 of windbg. I am sure that in the past the !poolused
command displayed the current allocations for each tag. I am looking at a
dump and it looks like the display is a total of all allocations, not the
current ones. For example, the non paged usage for AFdp is 4266791656. This
has to be a running total which makes it pretty useless.
Bill Wandel
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer