WER Functions
The following functions are used in Windows Error Reporting. For examples that use these functions, see samples in the Windows SDK under WinBase\WindowsErrorReporting and WinBase\Debug\FailFast.
In this section
| Topic | Description |
|---|---|
|
Excludes the specified application from error reporting. | |
|
WER calls this function to determine whether the exception handler is claiming the crash. | |
|
WER calls this function to let you customize the debugger launch options and launch string. | |
|
WER can call this function multiple times to get the report parameters that uniquely describe the problem. | |
|
Enables an application that performs its own exception handling to report faults to Microsoft. | |
|
Adds the specified application to the list of applications that are to be excluded from error reporting. | |
|
Frees up the memory used to store a report key string. This should be called after each successive call to WerStoreGetFirstReportKey or WerStoreGetNextReportKey, once the particular report key string has been used and is no longer needed. | |
|
Retrieves the fault reporting settings for the specified process. | |
|
Registers a process to be included in the error report along with the main application process. Optionally specifies a thread within that registered process to get additional data from. | |
|
Registers a path relative to the local app store for the calling application where Windows Error Reporting (WER) should save a copy of the diagnostic memory dump that WER collects when one of the processes for the application stops responding. | |
|
Registers app-specific metadata to be collected (in the form of key/value strings) when WER creates an error report. | |
|
Marks a memory block (that is normally included by default in error reports) to be excluded from the error report. | |
|
Registers a file to be collected when WER creates an error report. | |
|
Registers a memory block to be collected when WER creates an error report. | |
|
Registers a custom runtime exception handler that is used to provide custom error reporting for crashes. | |
|
Removes the specified application from the list of applications that are to be excluded from error reporting. | |
|
Adds a dump of the specified type to the specified report. | |
|
Adds a file to the specified report. | |
|
Closes the specified report. | |
|
Creates a problem report that describes an application event. | |
|
Initiates "no response" reporting on the specified window. | |
|
Sets the parameters that uniquely identify an event for the specified report. | |
|
Sets the user interface options for the specified report. | |
|
Submits the specified report. | |
|
Sets the fault reporting settings for the current process. | |
|
Closes the collection of stored reports. | |
|
Gets a reference to the first report in the report store. | |
|
Gets a reference to the next report in the error report store. | |
|
Opens the collection of stored error reports. | |
|
Retrieves metadata about a report in the store. | |
|
Removes a process from the list of additional processes to be included in the error report. | |
|
Cancels the registration that was made by calling the WerRegisterAppLocalDump function to specify that Windows Error Reporting (WER) should save a copy of the diagnostic memory dump that WER collects when one of the processes for the application stops responding. | |
|
Removes an item of app-specific metadata being collected during error reporting for the application. | |
|
Removes a memory block that was previously marked as excluded (it will again be included in error reports). | |
|
Removes a file from the list of files to be added to reports generated for the current process. | |
|
Removes a memory block from the list of data to be collected during error reporting for the application. | |
|
Removes the registration of your WER exception handler. |
Obsolete Functions
The following functions are obsolete and are provided only for compatibility: