2.2.3.1 Application Fault or Hang Reports
For user-mode error reports, the CER client MUST obtain the following information from the system to create this error signature.
|
Parameter |
Description |
|---|---|
|
AppName |
The file name of the faulting application binary. This MUST be between 1 and 64 characters long. |
|
AppVer |
The file version of the faulting application binary obtained from the file descriptor. This MUST be between 1 and 24 characters long. |
|
ModName |
The file name of the faulting module binary. This MUST be between 1 and 64 characters long. |
|
ModVer |
The file version of the faulting module binary obtained from the file descriptor. This MUST be between 1 and 24 characters long. |
|
Offset |
The code location in the faulting binary where the exception occurred (in hexadecimal without a leading 0x identifier). The offset value MUST be the full length specified by the architecture of the faulting process; for example, a valid 32-bit offset is "0000abcd", and a valid 64-bit offset is "0000abcd12345678". |
The error subpath for these types of reports MUST be composed using the error signature as follows: "<AppName>\<AppVer>\<ModName>\<ModVer>\<Offset>".
The specific file paths used in making this type of report MUST be as follows:
<UNC file share path>\cabs\<AppName>\<AppVer>\<ModName>\<ModVer>\<Offset>\<error reporting file>
<UNC file share path>\cabs\<AppName>\<AppVer>\<ModName>\<ModVer>\<Offset>\hits.log
<UNC file share path>\status\<AppName>\<AppVer>\<ModName>\<ModVer>\<Offset>\status.txt
<UNC file share path>\counts\<AppName>\<AppVer>\<ModName>\<ModVer>\<Offset>\count.txt