DebugDiag v1.1 Available!
Version 1.1 of the Debug Diagnostic Tool is now available on the Microsoft download site (download). This version contains many fixes and features, including:
- IE7, Vista, and Win64 compatibility fixes
- Leak rule improvements (dump on memory thresholds)
- LeakTrack improvements (‘fasttrack’ feature, injection fixes)
- Analysis improvements
- Allow custom script in crash rule actions
- Managed call stack resolution
- .NET exceptions support
- Debugger events support
- Data access components and socket support
- Sample scripts included
Please contact dbgdiag@microsoft.com for questions/feedback on v1.1 or feature requests for v2.0. Your feedback helps us prioritize and allocate necessary resources for future development on the tool.
HAPPY DEBUGGING!
Comments
Anonymous
July 26, 2007
Hello, I got into situation, where I needed to dump worker process reported unhealthy, as described in KB article http://support.microsoft.com/default.aspx/kb/828222/en-us I had debugdiag already installed on web server and I didn't want to install another debugger on production machine, so I was finding a way how to use debugdiag to dump such a process. Didn't find a lot in the documentation, so after looking into debugdiag TLBs for a while, I created the following vbscript, that should do the job: '------------- Dim pid Dim controller Dim process If Not wscript.arguments.named.exists("PID") Then wscript.quit End If pid=CInt(wscript.arguments.named("PID")) Set controller=CreateObject("dbgsvc.controller") For Each process In controller.processes If process.ProcessID=pid Then dumpname=process.createdump("Deadlock_Dump","I:DebugDiag") process.terminateprocess Exit For End If Next Set controller=Nothing '-------------------- Script is supposed to be a batch file to be executed when process orphans. Seems to be working on my test machine, now I'm going to use it on server I'm troubleshooting. Is this type of use of debugdiag supported? Will the debugdiag documentation be enhanced to cover this type of use? thanks, JiriAnonymous
June 07, 2012
Link is dead try this Debug Diagnostic Tool v1.2 www.microsoft.com/.../details.aspx