Function Prototype

vkDestroyDebugReportCallbackEXT

Destroy a debug report callback object

To destroy a VkDebugReportCallbackEXT object, call:

void vkDestroyDebugReportCallbackEXT(
    VkInstance instance,
    VkDebugReportCallbackEXT callback,
    const VkAllocationCallbacks* pAllocator);

instance is the instance where the callback was created.
callback is the VkDebugReportCallbackEXT object to destroy. callback is an externally synchronized object and must not be used on more than one thread at a time. This means that vkDestroyDebugReportCallbackEXT must not be called when a callback is active.
pAllocator controls host memory allocation as described in the Memory Allocation chapter.

Valid Usage

VUID-vkDestroyDebugReportCallbackEXT-instance-01242

If VkAllocationCallbacks were provided when callback was created, a compatible set of callbacks must be provided here

VUID-vkDestroyDebugReportCallbackEXT-instance-01243

If no VkAllocationCallbacks were provided when callback was created, pAllocator must be NULL

Valid Usage (Implicit)

VUID-vkDestroyDebugReportCallbackEXT-instance-parameter

instance must be a valid VkInstance handle

VUID-vkDestroyDebugReportCallbackEXT-callback-parameter

If callback is not VK_NULL_HANDLE, callback must be a valid VkDebugReportCallbackEXT handle

VUID-vkDestroyDebugReportCallbackEXT-pAllocator-parameter

If pAllocator is not NULL, pAllocator must be a valid pointer to a valid VkAllocationCallbacks structure

VUID-vkDestroyDebugReportCallbackEXT-callback-parent

If callback is a valid handle, it must have been created, allocated, or retrieved from instance

Host Synchronization

Host access to callback must be externally synchronized ::