Fix minor issue in vkCreateInstance extension loop

Extension checking in vkCreateInstance would simply loop through the first extension requested. This bug did not show up earlier (or at all) because erroneous situations would cause early exits in the loader. Bug: b/125943360 Change-Id: Id664f46d09dce1b3530670ae826314b26797b5be Reviewed-on: https://swiftshader-review.googlesource.com/c/25368Tested-by: Hernan Liatis <hliatis@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Fix minor issue in vkCreateInstance extension loop
9b433073 · Hernan Liatis · 8c1e8f1f · 9b433073
Commit 9b433073 authored Feb 22, 2019 by Hernan Liatis
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

libVulkan.cpp src/Vulkan/libVulkan.cpp +1 -1

No files found.
--- a/src/Vulkan/libVulkan.cpp
+++ b/src/Vulkan/libVulkan.cpp
@@ -107,7 +107,7 @@ VKAPI_ATTR VkResult VKAPI_CALL vkCreateInstance(const VkInstanceCreateInfo* pCre
 	for (uint32_t i = 0; i < pCreateInfo->enabledExtensionCount; ++i)
 	{
-		const char* currentExtensionName = *(pCreateInfo->ppEnabledExtensionNames);
+		const char* currentExtensionName = pCreateInfo->ppEnabledExtensionNames[i];
 		uint32_t extensionPropertiesCount = sizeof(instanceExtensionProperties) / sizeof(instanceExtensionProperties[0]);
 		bool foundExtension = false;