KhronosGroup / KhronosGroup/Vulkan-ValidationLayers

(feature request): dump the parameters passed to the barrier when reporting sync validation error

Open
#8,068 1 comment 0 reactions 0 assignees View on GitHub
Enhancement Synchronization
Dominant language
C++
Stars
1k
Forks
504
Avg merge
11h 35m
Merged PRs (30d)
224

Description

When validation layer reports a sync validation layer for a layout transition, it doesn't dump the parameters passed to the barrier call.
E.g.

SYNC-HAZARD-WRITE-AFTER-READ ] Object 0: handle = 0x1fb5b0cfaf0, type = VK_OBJECT_TYPE_QUEUE; | MessageID = 0x376bc9df | vkQueueSubmit(): Hazard WRITE_AFTER_READ for entry 0, VkCommandBuffer 0x1fb5b339e10[TaskScheduler_CommandList[1247]], Submitted access info (submitted_usage: SYNC_IMAGE_LAYOUT_TRANSITION, command: vkCmdPipelineBarrier2KHR, seq_no: 1, VkImage 0xa4725a0000006c34[SwapChainTexture], reset_no: 1)

It would make the user's life much easier if it could also dump the parameters passed to the barrier call?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the sync validation error for a layout transition involving vkCmdPipelineBarrier2KHR, then trace how the validation layer assembles that report. Done means the error output also includes the parameters passed to the barrier call; the payload does not name a source file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.