OutOfProcessExceptionEventSignatureCallback callback function

WER can call this function multiple times to get the report parameters that uniquely describe the problem.

The PFN_WER_RUNTIME_EXCEPTION_EVENT_SIGNATURE type defines a pointer to this callback function. You must use "OutOfProcessExceptionEventSignatureCallback" as the name of the callback function.

Syntax


HRESULT WINAPI OutOfProcessExceptionEventSignatureCallback(
  _In_     PVOID pContext,
  _In_     const PWER_RUNTIME_EXCEPTION_INFORMATION pExceptionInformation,
  _In_     DWORD dwIndex,
  _Out_    PWSTR pwszName,
  _Inout_  PDWORD pchName,
  _Out_    PWSTR pwszValue,
  _Inout_  PDWORD pchValue
);

Parameters

pContext [in]

A pointer to arbitrary context information that you specified when you called the WerRegisterRuntimeExceptionModule function to register the exception handler.

pExceptionInformation [in]

A WER_RUNTIME_EXCEPTION_INFORMATION structure that contains the exception information.

dwIndex [in]

The index of the report parameter. Valid values are 0 to 9. The first call to this function must set the index to 0, and each successive call must increment the index value sequentially.

pwszName [out]

A caller-allocated buffer that you use to specify the parameter name.

pchName [in, out]

The size, in characters, of the pwszName buffer. The size includes the null-terminating character.

pwszValue [out]

A caller-allocated buffer that you use to specify the parameter value.

pchValue [in, out]

The size, in characters, of the pwszValue buffer. The size includes the null-terminating character.

Return value

Return S_OK on success. If you return other failure codes, WER reverts to its default crash reporting behavior.

Remarks

You must implement this function in your exception handler DLL.

To generate error reports for application-specific issues, the application must create a short description of the problem using a few basic pieces of information called report parameters. Report parameters include information such as the application name, application version, module name, module version, and error code. The combination of these report parameters describes a unique problem.

WER calls this callback function only if you set the pbOwnershipClaimed parameter of your OutOfProcessExceptionEventCallback callback function to TRUE. The pdwSignatureCount parameter of OutOfProcessExceptionEventCallback determines the number of times that WER will call this callback function.

Requirements

Minimum supported client

Windows 7 [desktop apps only]

Minimum supported server

Windows Server 2008 R2 [desktop apps only]

Header

Werapi.h

See also

WerRegisterRuntimeExceptionModule

 

 

Community Additions

ADD
Show:
© 2014 Microsoft