From: Mark Young <marky@lunarg.com>
Date: Sat, 5 Feb 2022 00:02:52 +0000 (-0700)
Subject: Fix loader logging of VUIDs
X-Git-Tag: upstream/v1.3.207~37
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=b30b2aec84d92605cf6feefc2b22f0a3ffdf9297;p=platform%2Fupstream%2FVulkan-Loader.git

Fix loader logging of VUIDs

The loader was logging some VUID failures and it was sending them to the general
message output.  Send the information also to the validation stream to make sure
that if anyone enables validation filtering they will still see those errors
---

diff --git a/loader/log.c b/loader/log.c
index d424436a..f022666b 100644
--- a/loader/log.c
+++ b/loader/log.c
@@ -121,7 +121,9 @@ void loader_log(const struct loader_instance *inst, VkFlags msg_type, int32_t ms
         if ((msg_type & VULKAN_LOADER_PERF_BIT) != 0) {
             type = VK_DEBUG_UTILS_MESSAGE_TYPE_PERFORMANCE_BIT_EXT;
         } else if ((msg_type & VULKAN_LOADER_VALIDATION_BIT) != 0) {
-            type = VK_DEBUG_UTILS_MESSAGE_TYPE_VALIDATION_BIT_EXT;
+            // For loader logging, if it's a validation message, we still want to also keep the general flag as well
+            // so messages of type validation can still be triggered for general message callbacks.
+            type = VK_DEBUG_UTILS_MESSAGE_TYPE_GENERAL_BIT_EXT | VK_DEBUG_UTILS_MESSAGE_TYPE_VALIDATION_BIT_EXT;
         } else {
             type = VK_DEBUG_UTILS_MESSAGE_TYPE_GENERAL_BIT_EXT;
         }