The analysis engine reads the metadata files to determine which analysis extension plugins should be loaded. When the !analyze command runs in the debugger, the analysis engine looks in the extension file path for metadata files that have the. For example, if your DLL and metadata file are in the folder named c:\MyAnalyzer, enter the command. extpath command to add your directory to the extension file path. Place the metadata file in the same directory as your DLL. For information about how to create a metadata file, see Metadata Files for Analysis Extensions. For example, if your DLL is named MyAnalyzer.dll, your metadata file must be named MyAnalyzer.alz. Create a metadata file that has the same name as your DLL and an extension of.Create a DLL that exports an _EFN_Analyze function. To write an analysis extension plugin and make it available to !analyze, follow these steps. When !analyze runs, it locates, loads, and runs the appropriate analysis extension plugins. When you write an analysis extension plugin, you also write a metadata file that describes the situations for which you want your plugin to be called. By providing an analysis extension plugin, you can participate in the analysis of a bug check or an exception in a way that is specific to your own component or application. You can extend the capabilities of the !analyze debugger command by writing an analysis extension plugin.
0 Comments
Leave a Reply. |