Checking a dump file for WCF throttles

re: Checking a dump file for WCF throttles

Dustin Metzgar — Wed, 02 Feb 2011 01:37:17 GMT

Cool! I'll be able to use this in some of my debugging work.

re: Checking a dump file for WCF throttles

Naveen — Wed, 02 Feb 2011 01:26:31 GMT

No I was doing it on x64 that's the reason for .printf "%mu ", poi(${myobj}+20)+c

I have a platform independent dumpstring script as part of scripts

j $ptrsize = 8 'aS !ds .printf "%mu \n", c+';'aS !ds .printf "%mu \n", 10+'

So I could use something like this without being worried about x86/x64

0:000> !ds 00000000023620b8

MaxConcurrentInstances

re: Checking a dump file for WCF throttles

Naveen — Wed, 02 Feb 2011 01:25:53 GMT

No I was doing it on x64 that's the reason for .printf "%mu ", poi(${myobj}+20)+c

I have a platform independent dumpstring script as part of scripts

j $ptrsize = 8 'aS !ds .printf "%mu \n", c+';'aS !ds .printf "%mu \n", 10+'

So I could use something like this without being worried about x86/x64

0:000> !ds 00000000023620b8

MaxConcurrentInstances

re: Checking a dump file for WCF throttles

Dustin Metzgar — Wed, 02 Feb 2011 00:44:48 GMT

Good tip Naveen! I think you want .printf "%mu ", poi(${myobj}+20)+10 though. +10 goes to the first char. Thanks!

re: Checking a dump file for WCF throttles

Naveen — Tue, 01 Feb 2011 23:59:59 GMT

Good one. I would probably write the same script something like this

.foreach (myobj {!dumpheap -mt 000007feee769c00 -short}) {.printf "%mu ", poi(${myobj}+20)+c;.printf "%p", poi(${myobj}+34);.printf "%p \n", poi(${myobj}+30)}

Which would give the output like this

MaxConcurrentInstances 0000000000000017 0000001700000200

MaxConcurrentSessions 000000000000000a 0000000a00000200

MaxConcurrentInstances 000000000000002b 0000002b00000200

This will just avoid all the noise.