DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps

Link Listing - May 21, 2008

Christopher Steen — Thu, 22 May 2008 08:09:21 GMT

ASP.NET A New Tutorial Series on Master Pages [Via: Scott Mitchell ] Using parent page properties in...

Interesting Finds: 2008.05.24

gOODiDEA.NET — Sat, 24 May 2008 18:13:34 GMT

Debug ASP.NET Tips: What to gather to troubleshoot - part 6 - Recycle due to memoryLimit DebugDiag 1

Interesting Finds: 2008.05.24

gOODiDEA — Sat, 24 May 2008 18:14:18 GMT

DebugASP.NETTips:Whattogathertotroubleshoot-part6-RecycleduetomemoryLimitDebugDiag...

IIS Debug Diag info

Steve Schofield Weblog — Fri, 30 May 2008 06:49:00 GMT

A co-worker posted a how-to using IIS Debug Diag . After going through this process, I have a new found

re: DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps

Michael G — Sat, 31 May 2008 04:50:21 GMT

Out of curiosity, do you see any downside to using userdump.exe? I tends to be a little less "noisy" than adplus, so I typicaly ask customers to run it instead.

They don't need to worry their pretty little heads about "symbol not found" errors and such.

re: DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps

Tess — Sun, 01 Jun 2008 20:09:30 GMT

I haven't used userdump in ages, and can't remember the details about it, but assuming that it is just taking a memory dump right when you run userdump I don't see any issues with it...

Windows 디버거 (WinDBG, DebugDiag 1.1) 링크

Yong Hee Park's Blog — Wed, 25 Jun 2008 08:54:57 GMT

이미 많은 분들이 이들에 대한 글을 쓰셨기 때문에 간단하게 언급하고 링크나 달아 놓습니다. 윈도우에서 응용프로그램 디버깅을 위해서 많은 도구들이 사용 됩니다. 개발, 테스트, 배포순으로

re: DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps

Silverlight Travel — Mon, 20 Oct 2008 10:53:48 GMT

Thanks for your "which one should I use".

It was helpful for me to decide.

Regards

Peter Loebel

re: DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps

michalka — Thu, 11 Jun 2009 16:52:48 GMT

Hi Tess,

This is a very useful post- thank you!

We have a reproducible scenario where we run a specific component and we see that both virtual and private bytes are rising and not fully released.

We want to trace the source of the leak and we thought of using the DebugDiag.

We have a few questions regarding how to use it.

Does the information about the allocations is gathered from the injected dll? When the 'Memory and Handle leak' rule is running, what exactly is the purpose of the memory dumps in the sense of the memory leak investigation? Should the memory dump be taken when the allocations should have been released already?

In that case, we can create a 'Memory and handle leak' rule for our process, run the scenario and take a memory dump when it ends, is that correct?

Thank you,

Michal

re: DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps

Tess — Mon, 15 Jun 2009 10:42:52 GMT

hi michalka,

You would start leaktracking before you start reproducing, and if your repro is very short you should go into tools/options and tell it to start tracking stacks immediately instead of after 15 minutes.

Then at the end of your repro (when you have leaked) you generate a full dump and this then contains all the info about the leak, i.e. the allocations and the stacks making these allocations etc.

The injected dll keeps track of all this in memory, and thus this is why you need a dump, since you need to get to this memory. You would then run it through the analysis portion and it will summarize all the data it has

re: DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps

Petter — Mon, 26 Oct 2009 18:21:18 GMT

Is DebugDiag 1.1 supposed to work with 64 dumps?

I'm trying to analyze a dump from a W2008 X64 server on another one and the script fails with "Unkown error" on line 10098:

m_IsISAPIExtension = m_dbgModule.IsISAPIExtension

re: DebugDiag 1.1 or Windbg, which one should I use? and how do I gather memory dumps

Tess — Tue, 27 Oct 2009 07:31:13 GMT

HI Petter,

Debug Diag 1.1 currently doesnt work neither on 2008 nor on 64bit machines. The team behind debug diag is currently working on a version that should accommondate both but for now you have to use windbg. There is an RC of the new debug diag that you can get if you open a support case with microsoft (through http://support.microsoft.com) but unfortunately it does not work on 2008, as of yet at least.