For all of you who have been asking me if there is a 64bit version of Debug Diag (used to debug 64 bit processes), I am happy to say that yes, Debug Diag 1.1 64bit is now released.
You can download it here:
And an updated whitepaper talking about how to use it is available here:
Neither this version (nor the 32bit one) officially support debugging/analyzing on Vista/2008/Win7 because of some known compatibility issues (being looked at for future versions), however for a lot of tasks it works quite well on those operating systems as well.
Thanks for the heads up ! I really hated to have to install windbg on a customer machine, just to create a memory dump...
Thanks a million for the update. I was about to go crazy without this!
White paper on DebugDiag - typo:
Installing DebugDiag Manually for Enterprise deployment
3. Run the following commands:
Shouldn't it be
o Regsvr32.exe CrashHangExt.dll
Great work! Thanks a lot for sharing!
John, Tnx, I'll let them know and update
Jerome Laban: AFAIK it is enough to copy the windbg files files to the target machine, you don't need to install it if you only need to create a dump.
Seems I can install Analysis only tool on Windows Server 2008? I think "a lot of task" should include other stuff....
I'm having the same issue as Forrest.. windows server 2008 (.net 3.5 sp1) and it wont install anything but the analysis only version. I triple checked to make sure I didn't have any pervious packages containing 1.0. It's a 64 bit install of server.
Just found the answer to my own question. It doesn't run in IIS7.0 on windows server 2008 yet. You have to manually create dumps:
I have a problem with a .NET app on a Windows 7 x64 machine. I think Debug Diag does not support Windows 7. Is there any other way to automatically create a memory dump on a hang or unhandled exception of a .NET app?
thanks for the good info, continued to write for other interesting info. Good luck!
Thanks for the file links, exactly what I was looking for.
there is no way to truck a memory on server 2008.
ms sucks !!!!!!!
Debug Diag 1.2 will do this if you read some of my later blog posts.
Apparently, there is still no DebugDiag for Windows Server 2008. I managed to Create a Dump File of w3wp.exe from Windows Task Manager. Then I opened it with DebugDiag 64-bit Analyser. Now I have to figure out how to read this report... it does not really tell you which class is creating the issue. Should I use windbg?