Custom Analysis Debugger Extension Reference
This topic describes the available custom analysis extension APIs.
In this section
| Topic | Description |
|---|---|
|
When you write an Analysis Extension, you must implement and export an _EFN_Analyze function. When the !analyze debugger command runs, it calls your _EFN_Analyze so that you can participate in the analysis of a bug check or exception. | |
|
A DebugFailureAnalysis object has a collection of failure analysis entries (FA entries). Each FA entry is represented by an FA_ENTRY structure. For more information, see Failure Analysis Entries, Tags, and Data Types. | |
|
A DebugFailureAnalysis object has a collection of failure analysis entries (FA entries). Each FA entry has a tag, and each tag is associated with one of the data types in the FA_ENTRY_TYPE enumeration. For more information, see Failure Analysis Entries, Tags, and Data Types. | |
|
The values in the DEBUG_FAILURE_TYPE enumeration indicate the type of a failure. | |
|
The values of DEBUG_FLR_PARAM_TYPE enumeration are tags that indicate the kind of information that is stored in failure analysis entry. | |
|
A value in the FA_EXTENSION_PLUGIN_PHASE enumeration is passed to the _EFN_Analyze function to specify which phase of the analysis is currently in progress. | |
|
When the !analyze debugger command runs, the analysis engine can load and run extension analysis plug-ins. | |