fix null handling of array fields in autogen properties #2518
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 8bb1603.
0xcaff
changed the title
0xcaff
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Upon closer inspection of
VkPhysicalDeviceHostImageCopyPropertiesEXTit appears the nullability of thepCopySrcLayoutsandpCopyDstLayoutswas not handled correctly.These changes ensure that if an array field has a null value, its value is set to
Noneinstead of trying to dereference the pointer. It does not yet do one request for the size and a second for the values as outlined in the docs. This will be done in a follow up PR.Original Bug Report: https://discord.com/channels/937149253296476201/937153798982479912/1230477146062061629
vulkaninfo from crashing device
vulkaninfo.txt
Changelog