Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example 22 segfaults #340

Open
rwa opened this issue Jun 5, 2023 · 1 comment
Open

Example 22 segfaults #340

rwa opened this issue Jun 5, 2023 · 1 comment

Comments

@rwa
Copy link

rwa commented Jun 5, 2023

I have successfully compiled and run most of the examples, until I get to example 22.

Then I get:
validation layer: Validation Error: [ VUID-vkCmdDrawIndexed-None-02697 ] Object 0: handle = 0x130000000013, type = VK_OBJECT_TYPE_PIPELINE; Object 1: handle = 0x120000000012, type = VK_OBJECT_TYPE_PIPELINE_LAYOUT; Object 2: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_PIPELINE_LAYOUT; | MessageID = 0x9888fef3 | vkCmdDrawIndexed(): VkPipeline 0x130000000013[] defined with VkPipelineLayout 0x120000000012[] is not compatible for maximum set statically used 0 with bound descriptor sets, last bound with VkPipelineLayout 0x0[] The Vulkan spec states: For each set n that is statically used by the VkPipeline bound to the pipeline bind point used by this command, a descriptor set must have been bound to n at the same pipeline bind point, with a VkPipelineLayout that is compatible for set n, with the VkPipelineLayout used to create the current VkPipeline, as described in Pipeline Layout Compatibility (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-vkCmdDrawIndexed-None-02697) validation layer: Validation Error: [ UNASSIGNED-CoreValidation-DrawState-DescriptorSetNotBound ] Object 0: handle = 0x5558ff83f1c0, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0xcde11083 | vkCmdDrawIndexed(): VkPipeline 0x130000000013[] uses set #0 but that set is not bound. Segmentation fault (core dumped)

I have copied and pasted the example fresh from the repo, so I'm not sure what's going on here. I tried to interpret this error message but didn't make much headway. This is on an Ubuntu linux system.

@chuigda
Copy link
Contributor

chuigda commented Sep 25, 2023

This should be the expected behaviour. In chapater 22 the descriptor set layout get specified in the pipeline, but with actually no descriptor set provided. Chapater 23 would fix this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants