DebugDiag v2 is Now Out
The DebugDiag development team is very excited to announce the general availability of DebugDiag 2.0. The long waited DebugDiag 2.0 comes now with the new analysis engine fully converted to .NET to allow for faster analysis rule development. The tool comes also with a number of new features in the Collection and Analysis modules such as .NET 4.5 support,CLRMD integration, C# and XAML sample rules, Detailed 1st chance exception logging…etc.
The Debug Diagnostic Tool is a tool designed to help troubleshoot performance issues with Internet Information Services (IIS). Even though the tool was designed with troubleshooting IIS in mind it can be used to identify performance issues for any process...
The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or fragmentation, and crashes in any user-mode process. The tool includes built-in analysis rules focused on Internet Information Services (IIS) applications, web data access components, COM+, SharePoint and related Microsoft technologies
Date Published: 10/2/2013
DebugDiagx64.msi, 21.4 MB
DebugDiagx86.msi, 16.6 MB
Debugdiag 2.0 introduces a new analysis engine host with built-in reporting framework that can be accessed from .NET. This new analysis engine simplifies analysis rule development in .NET.
- DebugDiag 1.0 released as part of the IIS Diagnostic Toolkit and as a standalone tool (x86 only).
- DebugDiag 1.1 released as a standalone tool only (x86 and limited x64 support).
- DebugDiag 1.2 released as a standalone tool only (x86 and full x64 support).
DebugDiag is composed of two main modules: Collection and Analysis
The collection module is composed of three main components: The Debugging service, the debugger host and the user interface. It is the base install component of the tool.
- Debugging service: DbgSvc.exe. The Debugging Service performs the following tasks: ...
- Debugger Host : DbgHost.exe. The Debugger Host hosts the Windows Symbolic Debugger Engine (dbgeng.dll) to attach to processes and generate memory dumps. Dbghost.exe has no dependency on the service “DbgSvc.exe” and can be used separately.
- User Interface: DebugDiag.Collection.exe. The User Interface allows generation of control scripts, manual dump generation, displaying of rules status…etc. It is composed of two views: ...
The analysis module is selected by default in a typical install; however, you can deselect the feature if not needed. The analysis module requires .NET 4.0 installed on the system.
- Analysis Engine: dbglib.dll, DebugDiag.DotNet.dll The analysis engine loads in the Analysis UI. It uses the Windows Symbolic Debugger Engine (dbgeng.dll) to access userdump data. It exposes this data via a rich API set that you can call from .NET code.
- Analysis UI: DebugDiag.Analysis.exe The analysis UI is a .NET 4.0 executable that allows you to runs selected "Analysis Rules" against one or more memory dumps. ...
- Rule Builder: DebugDiag.RuleBuilder.exe The Rule builder UI is a .net 4.0 Workflow application that allows you to create simple workflow analysis rules...
This is one of those items that I don't need today, but know that I will need in the future and won't be able to remember where I saw it. That and I think it sounds kind of cool... :)
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)