Reputation: 4663
I want to use a new VK_EXT_debug_utils
. I did it in a couple of projects already and it worked fine, but today I found that vkSetDebugUtilsObjectNameEXT
throws a SIGSEGV
. I spent a good amount of time trying to figure out what were differences between a new project and the old ones. With blind attempts, I figured out that in the new project I didn't specify VK_KHR_SWAPCHAIN_EXTENSION_NAME
when created a device (because I don't need it) and that caused a crash somehow. I searched in a documentation but could not find any mention of this behavior. Did I miss something important?
Upd.: on Windows, the problem exists as well.
Upvotes: 1
Views: 272
Reputation: 186
(Edited: Now fixed) I just saw this issue. I looked into it quickly by modifying one of Sascha Willems examples and I was able to reproduce this. It is a Vulkan loader bug, not a driver bug. I created a Vulkan loader bug here and resolved the issue.
If you build your own Vulkan loader, you can get a fix now. Otherwise, you'll have to wait for our next SDK release.
Sorry, but a huge thanks for catching this.
Upvotes: 2