From 8d2bcdaab54dadf94c2075e655e7d7030528a5d5 Mon Sep 17 00:00:00 2001
From: "Enrico Weigelt, metux IT consult" <info@metux.net>
Date: Mon, 30 Jun 2025 13:44:22 +0200
Subject: [PATCH] Xnest: fix analyzer warning on uninitialized `DefaultVisual`

In xnestOpenScreen(), some compilers/analyzers spitting out a false alarm on
`defaultVisual` field potentially used uninitialized. This can't practically
happen, but not all compilers/analyzers really can see that.

Adding a zero initializer doesn't cost us anything, so silencing that false
alarm is trivial.

Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
---
 hw/xnest/Screen.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hw/xnest/Screen.c b/hw/xnest/Screen.c
index 25a7ccae8..7bf522a55 100644
--- a/hw/xnest/Screen.c
+++ b/hw/xnest/Screen.c
@@ -164,7 +164,7 @@ Bool
 xnestOpenScreen(ScreenPtr pScreen, int argc, char *argv[])
 {
     unsigned long valuemask;
-    VisualID defaultVisual;
+    VisualID defaultVisual = 0;
     int rootDepth;
     miPointerScreenPtr PointPriv;