Confirmed users
1,798
edits
Release Management/WER Investigation: Difference between revisions
Jump to navigation
Jump to search
Release Management/WER Investigation (view source)
Revision as of 23:42, 6 October 2011
, 6 October 2011→Cab File Contents (for collector/processor)
mNo edit summary |
|||
| Line 51: | Line 51: | ||
=== Cab File Contents (for collector/processor) === | === Cab File Contents (for collector/processor) === | ||
* WERInternalMetadata.xml - (possibly) not present if version.txt is. | * WERInternalMetadata.xml - (possibly) not present if version.txt is. Includes | ||
* AppCompat.txt (also all lower) - not present if WERDataCollectionFailure.txt is. | ** OSVersionInformation - windows version info, architecture, etc. | ||
** ProblemSignatures - event type (crash/hang), crashing executable name, exe version/timestamp, methodDef token of faulting method (?), and IL offset of faulting instruction (?) | |||
** DynamicSignatures - | |||
** SystemInformation - HW info. What's an MID? | |||
* AppCompat.txt (also all lower) - not present if WERDataCollectionFailure.txt is. Includes information on all images loaded by the process. | |||
* WERDataCollectionFailure.txt - includes error message if processing failed in MS. | * WERDataCollectionFailure.txt - includes error message if processing failed in MS. | ||
* version.txt - only | * version.txt - only came across this once. Only included OS version. | ||
* For crashes | * For crashes | ||
** ______.{m}dmp - minidump file. These types of dumps already appeared to be handled according to http://code.google.com/p/google-breakpad/wiki/ProcessorDesign | ** ______.{m}dmp - minidump file. These types of dumps already appeared to be handled according to http://code.google.com/p/google-breakpad/wiki/ProcessorDesign | ||