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

Debug utils terms #318

Merged
merged 2 commits into from
Feb 3, 2020
Merged

Conversation

lenny-lunarg
Copy link
Contributor

This fixes #116.

This PR addresses the bug where the loader returns an invalid function pointers when an application calls vkGetInstanceProcAddr on the methods from the VK_EXT_debug_utils extension. Previously, the function pointers would run fine, but they would never call into the driver. This makes them call into the driver.

I'd be lying if I said I was 100% happy with this change. I wound up adding terminators for each function in this extension because doing so allowed me to use the existing instance functionality for choosing which driver to call into. But I do think this should do the job. This is a very special case because debug utils is an instance extension that contains device level functions.

Change-Id: I9e08b59669bd301e3c5361ae4ea16102461fb34b
Change-Id: Ia59f3c34addca92cfa22f4396ea30deb445a1ffc
Copy link
Contributor

@pdaniell-nv pdaniell-nv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested with the NVIDIA driver and I can see it now calls down into the driver.

@lenny-lunarg lenny-lunarg merged commit 807f146 into KhronosGroup:master Feb 3, 2020
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

Successfully merging this pull request may close these issues.

Regression and incorrect handling of VK_EXT_debug_utils instance extension
2 participants