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. Optionally specifies a thread within that registered process to get additional data from. Registers a process to be included in the error report along with the main application process. Retrieves the fault reporting settings for the specified process. 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. WER can call this function multiple times to get the report parameters that uniquely describe the problem.Įnables an application that performs its own exception handling to report faults to Microsoft.Īdds the specified application to the list of applications that are to be excluded from error reporting.įrees up the memory used to store a report key string. PFN_WER_RUNTIME_EXCEPTION_EVENT_SIGNATURE 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. PFN_WER_RUNTIME_EXCEPTION_DEBUGGER_LAUNCH (ANSI)Įxcludes the specified application from error reporting. To develop Windows Error Reporting, you need these headers:įor programming guidance for this technology, see:Įxcludes the specified application from error reporting. Overview of the Windows Error Reporting technology.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |