vkSetDebugUtilsObjectNameEXT - Give a user-friendly name to an object

Valid Usage

• pNameInfo->objectType must not be OBJECT_TYPE_UNKNOWN

• pNameInfo->objectHandle must not be NULL_HANDLE
• If pNameInfo->objectHandle is the valid handle of an instance-level object, the Device identified by device must be a descendent of the same Instance as the object identified by pNameInfo->objectHandle
• If pNameInfo->objectHandle is the valid handle of a physical-device-level object, the Device identified by device must be a descendant of the same PhysicalDevice as the object identified by pNameInfo->objectHandle
• If pNameInfo->objectHandle is the valid handle of a device-level object, that object must be a descendent of the Device identified by device

Valid Usage (Implicit)

• device must be a valid Device handle

• pNameInfo must be a valid pointer to a valid DebugUtilsObjectNameInfoEXT structure

Host Synchronization

• Host access to pNameInfo->objectHandle must be externally synchronized

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

VK_EXT_debug_utils, DebugUtilsObjectNameInfoEXT, Device

vkSetDebugUtilsObjectTagEXT - Attach arbitrary data to an object

Valid Usage

• If pNameInfo->objectHandle is the valid handle of an instance-level object, the Device identified by device must be a descendent of the same Instance as the object identified by pNameInfo->objectHandle

• If pNameInfo->objectHandle is the valid handle of a physical-device-level object, the Device identified by device must be a descendant of the same PhysicalDevice as the object identified by pNameInfo->objectHandle
• If pNameInfo->objectHandle is the valid handle of a device-level object, that object must be a descendent of the Device identified by device

Valid Usage (Implicit)

• device must be a valid Device handle

• pTagInfo must be a valid pointer to a valid DebugUtilsObjectTagInfoEXT structure

Host Synchronization

• Host access to pTagInfo->objectHandle must be externally synchronized

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

VK_EXT_debug_utils, DebugUtilsObjectTagInfoEXT, Device

vkQueueBeginDebugUtilsLabelEXT - Open a queue debug label region

Command Properties

'

See Also

VK_EXT_debug_utils, DebugUtilsLabelEXT, Queue

vkQueueEndDebugUtilsLabelEXT - Close a queue debug label region

Description

The calls to queueBeginDebugUtilsLabelEXT and queueEndDebugUtilsLabelEXT must be matched and balanced.

Valid Usage

• There must be an outstanding queueBeginDebugUtilsLabelEXT command prior to the queueEndDebugUtilsLabelEXT on the queue

Valid Usage (Implicit)

• queue must be a valid Queue handle

Command Properties

'

See Also

VK_EXT_debug_utils, Queue

vkQueueInsertDebugUtilsLabelEXT - Insert a label into a queue

Command Properties

'

See Also

VK_EXT_debug_utils, DebugUtilsLabelEXT, Queue

vkCmdBeginDebugUtilsLabelEXT - Open a command buffer debug label region

Valid Usage (Implicit)

• commandBuffer must be a valid CommandBuffer handle

• pLabelInfo must be a valid pointer to a valid DebugUtilsLabelEXT structure
• commandBuffer must be in the recording state
• The CommandPool that commandBuffer was allocated from must support graphics, or compute operations
• This command must only be called outside of a video coding scope

Host Synchronization

• Host access to commandBuffer must be externally synchronized

• Host access to the CommandPool that commandBuffer was allocated from must be externally synchronized

Command Properties

'

See Also

VK_EXT_debug_utils, CommandBuffer, DebugUtilsLabelEXT

This function will call the supplied action between calls to cmdBeginDebugUtilsLabelEXT and cmdEndDebugUtilsLabelEXT

Note that cmdEndDebugUtilsLabelEXT is *not* called if an exception is thrown by the inner action.

vkCmdEndDebugUtilsLabelEXT - Close a command buffer label region

Description

An application may open a debug label region in one command buffer and close it in another, or otherwise split debug label regions across multiple command buffers or multiple queue submissions. When viewed from the linear series of submissions to a single queue, the calls to cmdBeginDebugUtilsLabelEXT and cmdEndDebugUtilsLabelEXT must be matched and balanced.

There can be problems reporting command buffer debug labels during the recording process because command buffers may be recorded out of sequence with the resulting execution order. Since the recording order may be different, a solitary command buffer may have an inconsistent view of the debug label regions by itself. Therefore, if an issue occurs during the recording of a command buffer, and the environment requires returning debug labels, the implementation may return only those labels it is aware of. This is true even if the implementation is aware of only the debug labels within the command buffer being actively recorded.

Valid Usage

• There must be an outstanding cmdBeginDebugUtilsLabelEXT command prior to the cmdEndDebugUtilsLabelEXT on the queue that commandBuffer is submitted to

• If commandBuffer is a secondary command buffer, there must be an outstanding cmdBeginDebugUtilsLabelEXT command recorded to commandBuffer that has not previously been ended by a call to cmdEndDebugUtilsLabelEXT

Valid Usage (Implicit)

• commandBuffer must be a valid CommandBuffer handle

• commandBuffer must be in the recording state
• The CommandPool that commandBuffer was allocated from must support graphics, or compute operations
• This command must only be called outside of a video coding scope

Host Synchronization

• Host access to commandBuffer must be externally synchronized

• Host access to the CommandPool that commandBuffer was allocated from must be externally synchronized

Command Properties

'

See Also

VK_EXT_debug_utils, CommandBuffer

vkCmdInsertDebugUtilsLabelEXT - Insert a label into a command buffer

Valid Usage (Implicit)

• commandBuffer must be a valid CommandBuffer handle

• pLabelInfo must be a valid pointer to a valid DebugUtilsLabelEXT structure
• commandBuffer must be in the recording state
• The CommandPool that commandBuffer was allocated from must support graphics, or compute operations
• This command must only be called outside of a video coding scope

Host Synchronization

• Host access to commandBuffer must be externally synchronized

• Host access to the CommandPool that commandBuffer was allocated from must be externally synchronized

Command Properties

'

See Also

VK_EXT_debug_utils, CommandBuffer, DebugUtilsLabelEXT

vkCreateDebugUtilsMessengerEXT - Create a debug messenger object

Valid Usage (Implicit)

• instance must be a valid Instance handle

• pCreateInfo must be a valid pointer to a valid DebugUtilsMessengerCreateInfoEXT structure
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid AllocationCallbacks structure
• pMessenger must be a valid pointer to a DebugUtilsMessengerEXT handle

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY

The application must ensure that createDebugUtilsMessengerEXT is not executed in parallel with any Vulkan command that is also called with instance or child of instance as the dispatchable argument.

See Also

VK_EXT_debug_utils, AllocationCallbacks, DebugUtilsMessengerCreateInfoEXT, DebugUtilsMessengerEXT, Instance

A convenience wrapper to make a compatible pair of calls to createDebugUtilsMessengerEXT and destroyDebugUtilsMessengerEXT

To ensure that destroyDebugUtilsMessengerEXT is always called: pass bracket (or the allocate function from your favourite resource management library) as the last argument. To just extract the pair pass (,) as the last argument.

vkDestroyDebugUtilsMessengerEXT - Destroy a debug messenger object

Valid Usage

• If AllocationCallbacks were provided when messenger was created, a compatible set of callbacks must be provided here

• If no AllocationCallbacks were provided when messenger was created, pAllocator must be NULL

Valid Usage (Implicit)

• instance must be a valid Instance handle

• If messenger is not NULL_HANDLE, messenger must be a valid DebugUtilsMessengerEXT handle
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid AllocationCallbacks structure
• If messenger is a valid handle, it must have been created, allocated, or retrieved from instance

Host Synchronization

• Host access to messenger must be externally synchronized

The application must ensure that destroyDebugUtilsMessengerEXT is not executed in parallel with any Vulkan command that is also called with instance or child of instance as the dispatchable argument.

See Also

VK_EXT_debug_utils, AllocationCallbacks, DebugUtilsMessengerEXT, Instance

vkSubmitDebugUtilsMessageEXT - Inject a message into a debug stream

Description

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

• The objectType member of each element of pCallbackData->pObjects must not be OBJECT_TYPE_UNKNOWN

Valid Usage (Implicit)

• instance must be a valid Instance handle

• messageSeverity must be a valid DebugUtilsMessageSeverityFlagBitsEXT value
• messageTypes must be a valid combination of DebugUtilsMessageTypeFlagBitsEXT values
• messageTypes must not be 0
• pCallbackData must be a valid pointer to a valid DebugUtilsMessengerCallbackDataEXT structure

See Also

VK_EXT_debug_utils, DebugUtilsMessageSeverityFlagBitsEXT, DebugUtilsMessageTypeFlagsEXT, DebugUtilsMessengerCallbackDataEXT, Instance

VkDebugUtilsObjectNameInfoEXT - Specify parameters of a name to give to an object

Description

Applications may change the name associated with an object simply by calling setDebugUtilsObjectNameEXT again with a new string. If pObjectName is either NULL or an empty string, then any previously set name is removed.

The graphicsPipelineLibrary feature allows the specification of pipelines without the creation of ShaderModule objects beforehand. In order to continue to allow naming these shaders independently, DebugUtilsObjectNameInfoEXT can be included in the pNext chain of PipelineShaderStageCreateInfo, which associates a static name with that particular shader.

Valid Usage

• If objectType is OBJECT_TYPE_UNKNOWN, objectHandle must not be NULL_HANDLE

• If objectType is not OBJECT_TYPE_UNKNOWN, objectHandle must be NULL_HANDLE or a valid Vulkan handle of the type associated with objectType as defined in the and Vulkan Handle Relationship table

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_DEBUG_UTILS_OBJECT_NAME_INFO_EXT

• objectType must be a valid ObjectType value
• If pObjectName is not NULL, pObjectName must be a null-terminated UTF-8 string

See Also

VK_EXT_debug_utils, DebugUtilsMessengerCallbackDataEXT, ObjectType, StructureType, setDebugUtilsObjectNameEXT

VkDebugUtilsObjectTagInfoEXT - Specify parameters of a tag to attach to an object

Description

The tagName parameter gives a name or identifier to the type of data being tagged. This can be used by debugging layers to easily filter for only data that can be used by that implementation.

Valid Usage (Implicit)

See Also

VK_EXT_debug_utils, ObjectType, StructureType, setDebugUtilsObjectTagEXT

VkDebugUtilsLabelEXT - Specify parameters of a label region

Valid Usage (Implicit)

See Also

VK_EXT_debug_utils, DebugUtilsMessengerCallbackDataEXT, StructureType, cmdBeginDebugUtilsLabelEXT, cmdInsertDebugUtilsLabelEXT, queueBeginDebugUtilsLabelEXT, queueInsertDebugUtilsLabelEXT

VkDebugUtilsMessengerCreateInfoEXT - Structure specifying parameters of a newly created debug messenger

Description

For each DebugUtilsMessengerEXT that is created the DebugUtilsMessengerCreateInfoEXT::messageSeverity and DebugUtilsMessengerCreateInfoEXT::messageType determine when that DebugUtilsMessengerCreateInfoEXT::pfnUserCallback is called. The process to determine if the user’s pfnUserCallback is triggered when an event occurs is as follows:

1. The implementation will perform a bitwise AND of the event’s DebugUtilsMessageSeverityFlagBitsEXT with the messageSeverity provided during creation of the DebugUtilsMessengerEXT object.

   1. If the value is 0, the message is skipped.

2. The implementation will perform bitwise AND of the event’s DebugUtilsMessageTypeFlagBitsEXT with the messageType provided during the creation of the DebugUtilsMessengerEXT object.

   1. If the value is 0, the message is skipped.
3. The callback will trigger a debug message for the current event

The callback will come directly from the component that detected the event, unless some other layer intercepts the calls for its own purposes (filter them in a different way, log to a system error log, etc.).

An application can receive multiple callbacks if multiple DebugUtilsMessengerEXT objects are created. A callback will always be executed in the same thread as the originating Vulkan call.

A callback can be called from multiple threads simultaneously (if the application is making Vulkan calls from multiple threads).

Valid Usage (Implicit)

See Also

PFN_vkDebugUtilsMessengerCallbackEXT, VK_EXT_debug_utils, DebugUtilsMessageSeverityFlagsEXT, DebugUtilsMessageTypeFlagsEXT, DebugUtilsMessengerCreateFlagsEXT, StructureType, createDebugUtilsMessengerEXT

VkDebugUtilsMessengerCallbackDataEXT - Structure specifying parameters returned to the callback

Description

Note

This structure should only be considered valid during the lifetime of the triggered callback.

Since adding queue and command buffer labels behaves like pushing and popping onto a stack, the order of both pQueueLabels and pCmdBufLabels is based on the order the labels were defined. The result is that the first label in either pQueueLabels or pCmdBufLabels will be the first defined (and therefore the oldest) while the last label in each list will be the most recent.

Note

pQueueLabels will only be non-NULL if one of the objects in pObjects can be related directly to a defined Queue which has had one or more labels associated with it.

Likewise, pCmdBufLabels will only be non-NULL if one of the objects in pObjects can be related directly to a defined CommandBuffer which has had one or more labels associated with it. Additionally, while command buffer labels allow for beginning and ending across different command buffers, the debug messaging framework cannot guarantee that labels in pCmdBufLables will contain those defined outside of the associated command buffer. This is partially due to the fact that the association of one command buffer with another may not have been defined at the time the debug message is triggered.

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CALLBACK_DATA_EXT

• pNext must be NULL or a pointer to a valid instance of DeviceAddressBindingCallbackDataEXT
• The sType value of each struct in the pNext chain must be unique
• flags must be 0
• If pMessageIdName is not NULL, pMessageIdName must be a null-terminated UTF-8 string
• pMessage must be a null-terminated UTF-8 string
• If queueLabelCount is not 0, pQueueLabels must be a valid pointer to an array of queueLabelCount valid DebugUtilsLabelEXT structures
• If cmdBufLabelCount is not 0, pCmdBufLabels must be a valid pointer to an array of cmdBufLabelCount valid DebugUtilsLabelEXT structures
• If objectCount is not 0, pObjects must be a valid pointer to an array of objectCount valid DebugUtilsObjectNameInfoEXT structures

See Also

VK_EXT_debug_utils, DebugUtilsLabelEXT, DebugUtilsMessengerCallbackDataFlagsEXT, DebugUtilsObjectNameInfoEXT, StructureType, submitDebugUtilsMessageEXT

VkDebugUtilsMessengerCreateFlagsEXT - Reserved for future use

Description

DebugUtilsMessengerCreateFlagsEXT is a bitmask type for setting a mask, but is currently reserved for future use.

See Also

VK_EXT_debug_utils, DebugUtilsMessengerCreateInfoEXT

VkDebugUtilsMessengerCallbackDataFlagsEXT - Reserved for future use

Description

DebugUtilsMessengerCallbackDataFlagsEXT is a bitmask type for setting a mask, but is currently reserved for future use.

See Also

VK_EXT_debug_utils, DebugUtilsMessengerCallbackDataEXT

VkDebugUtilsMessageSeverityFlagBitsEXT - Bitmask specifying which severities of events cause a debug messenger callback

Description

Note

The values of DebugUtilsMessageSeverityFlagBitsEXT are sorted based on severity. The higher the flag value, the more severe the message. This allows for simple boolean operation comparisons when looking at DebugUtilsMessageSeverityFlagBitsEXT values.

For example:

    if (messageSeverity >= VK_DEBUG_UTILS_MESSAGE_SEVERITY_WARNING_BIT_EXT) {
        // Do something for warnings and errors
    }

In addition, space has been left between the enums to allow for later addition of new severities in between the existing values.

See Also

VK_EXT_debug_utils, DebugUtilsMessageSeverityFlagsEXT, submitDebugUtilsMessageEXT

VkDebugUtilsMessageTypeFlagBitsEXT - Bitmask specifying which types of events cause a debug messenger callback

See Also

VK_EXT_debug_utils, DebugUtilsMessageTypeFlagsEXT

PFN_vkDebugUtilsMessengerCallbackEXT - Application-defined debug messenger callback function

Description

The callback returns a Bool32, which is interpreted in a layer-specified manner. The application should always return FALSE. The TRUE value is reserved for use in layer development.

Valid Usage

• The callback must not make calls to any Vulkan commands

See Also

VK_EXT_debug_utils, DebugUtilsMessengerCreateInfoEXT

VkDebugUtilsMessengerEXT - Opaque handle to a debug messenger object

Description

The debug messenger will provide detailed feedback on the application’s use of Vulkan when events of interest occur. When an event of interest does occur, the debug messenger will submit a debug message to the debug callback that was provided during its creation. Additionally, the debug messenger is responsible with filtering out debug messages that the callback is not interested in and will only provide desired debug messages.

See Also

VK_EXT_debug_utils, createDebugUtilsMessengerEXT, destroyDebugUtilsMessengerEXT