Blame SOURCES/0008-glamor-Dump-backtrace-on-GL-error.patch

b6a310
From 85638273f23338d06776cdb7bb422440f690038a Mon Sep 17 00:00:00 2001
b6a310
From: Olivier Fourdan <ofourdan@redhat.com>
b6a310
Date: Tue, 30 Mar 2021 08:48:25 +0200
b6a310
Subject: [PATCH xserver 08/27] glamor: Dump backtrace on GL error
b6a310
MIME-Version: 1.0
b6a310
Content-Type: text/plain; charset=UTF-8
b6a310
Content-Transfer-Encoding: 8bit
b6a310
b6a310
Currrently, when a GL error is triggered, glamor would log the error
b6a310
which may not be sufficient to trace it back to the cause of the error.
b6a310
b6a310
Also dump the backtrace which may give more information as to where the
b6a310
error comes from.
b6a310
b6a310
Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
b6a310
Reviewed-by: Martin Peres <martin.peres@mupuf.org>
b6a310
Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
b6a310
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1156
b6a310
(cherry picked from commit 3b265c59a6456f6e4abfb9e1694237bc56f1776a)
b6a310
---
b6a310
 glamor/glamor.c | 1 +
b6a310
 1 file changed, 1 insertion(+)
b6a310
b6a310
diff --git a/glamor/glamor.c b/glamor/glamor.c
b6a310
index 3baef4b9f..b8406f42d 100644
b6a310
--- a/glamor/glamor.c
b6a310
+++ b/glamor/glamor.c
b6a310
@@ -414,6 +414,7 @@ glamor_debug_output_callback(GLenum source,
b6a310
 
b6a310
     LogMessageVerb(X_ERROR, 0, "glamor%d: GL error: %*s\n",
b6a310
                screen->myNum, length, message);
b6a310
+    xorg_backtrace();
b6a310
 }
b6a310
 
b6a310
 /**
b6a310
-- 
b6a310
2.31.1
b6a310