A customer has supplied you with data from Windows Event Viewer about a crash. The log contains XML and you don't know which values are relevant.
The event log data will have a provider name of "Windows Error Reporting" or "Application Error".
The XML data is found on the "Details" tab with the XML View radio box selected.
<Provider Name="Windows Error Reporting" />
<TimeCreated SystemTime="2020-02-10T17:39:08.000000000Z" />
This is data from a test program that is designed to crash.
There the event log indicates a DLL, but no load address, two different addresses, an exception code and an offset from the start of the DLL. How do you decode this relative offset?
DbgHelpBrowser has an option specifically for this occasion.
The XML data indicates the crash happened in testDeliberateCrash.exe. Load this into DbgHelpBrowser being sure to load the correct build version and that the PDB file can be found so that symbols get loaded.
From the Query menu choose Find Symbol from Event Viewer XML crash log....
The Query Symbol by Absolute Address dialog is displayed.
Paste the XML data from the Event Viewer into the text field.
Click the Find Symbol button.
The appropriate location in the code is found and displayed.
The query options are not available for .Net and .Net executables as there is no direct translation from a crash address/offset to a .Net symbol.
Without having access to the compiled .Net method address and the compiled address to ILASM instruction offset data it is impossible to translate crash addresses/offsets to .Net functions.
The compiled address to ILAMS instruction offset data is only available in the context of a running .Net application attached to a .Net debugger or a .Net profiler.