vkDestroyDebugReportCallbackEXT

vkDestroyDebugUtilsMessengerEXT and vkDestroyDebugReportCallbackEXT are Vulkan API functions provided by the VK_EXT_debug_utils and VK_EXT_debug_report extensions. They destroy debug messenger or callback objects that were created to receive diagnostic messages from validation layers and other debug sources. Properly destroying these objects is part of cleanly shutting down a Vulkan application and ensures that resources allocated for debugging are released before terminating the Vulkan instance.

Both functions are instance-scoped, meaning they take a VkInstance as the first parameter and operate on a previously created debug messenger or callback. They do not return a value. Typical usage is to call the destroy function after you are finished with the messenger or callback and before destroying the Vulkan instance or during teardown.

Prototypes (textual):

- void vkDestroyDebugUtilsMessengerEXT(VkInstance instance, VkDebugUtilsMessengerEXT messenger, const VkAllocationCallbacks* pAllocator);

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

Notes:

- If the messenger/callback handle is VK_NULL_HANDLE, the function may perform no operation.

- pAllocator can be NULL to use the default allocation callbacks.

- These functions are optional and only available if the corresponding extension is enabled and loaded. In practice, you obtain the function pointers via a loader or vkGetInstanceProcAddr.

- It is recommended to destroy debug utilities before destroying the Vulkan instance to avoid use-after-free issues with internal structures.

In summary, vkDestroyDebugUtilsMessengerEXT and vkDestroyDebugReportCallbackEXT provide the final cleanup step for debug instrumentation, ensuring that resources allocated for diagnostic messaging are properly released.