Function Prototype
vkSubmitDebugUtilsMessageEXT
Inject a message into a debug stream
To intentionally submit a debug message, call:
void vkSubmitDebugUtilsMessageEXT(
VkInstance instance,
VkDebugUtilsMessageSeverityFlagBitsEXT messageSeverity,
VkDebugUtilsMessageTypeFlagsEXT messageTypes,
const VkDebugUtilsMessengerCallbackDataEXT* pCallbackData);
instanceis the debug stream’s VkInstance.messageSeverityis a VkDebugUtilsMessageSeverityFlagBitsEXT value specifying the severity of this event/message.messageTypesis a bitmask of VkDebugUtilsMessageTypeFlagBitsEXT specifying which type of event(s) to identify with this message.pCallbackDatacontains all the callback related data in the VkDebugUtilsMessengerCallbackDataEXT structure.
The call will propagate through the layers and generate callback(s) as
indicated by the message’s flags.
The parameters are passed on to the callback in addition to the
pUserData value that was defined at the time the messenger was
registered.
Valid Usage
VUID-vkSubmitDebugUtilsMessageEXT-objectType-02591
The objectType member of each element of
pCallbackData→pObjects must not be VK_OBJECT_TYPE_UNKNOWN
Valid Usage (Implicit)
VUID-vkSubmitDebugUtilsMessageEXT-instance-parameter
instance must be a valid VkInstance handle
VUID-vkSubmitDebugUtilsMessageEXT-messageSeverity-parameter
messageSeverity must be a valid VkDebugUtilsMessageSeverityFlagBitsEXT value
VUID-vkSubmitDebugUtilsMessageEXT-messageTypes-parameter
messageTypes must be a valid combination of VkDebugUtilsMessageTypeFlagBitsEXT values
VUID-vkSubmitDebugUtilsMessageEXT-messageTypes-requiredbitmask
messageTypes must not be 0
VUID-vkSubmitDebugUtilsMessageEXT-pCallbackData-parameter
pCallbackData must be a valid pointer to a valid VkDebugUtilsMessengerCallbackDataEXT structure