summaryrefslogtreecommitdiff
path: root/glamor
diff options
context:
space:
mode:
authorOlivier Fourdan <ofourdan@redhat.com>2021-03-30 08:48:25 +0200
committerOlivier Fourdan <ofourdan@redhat.com>2021-05-11 14:08:58 +0200
commit3b265c59a6456f6e4abfb9e1694237bc56f1776a (patch)
tree6f104b3c61c997bae8c47b031a1ffd56afbc146c /glamor
parent25d2f4948f0abd39e099b8ac69b7cb1dab38a10a (diff)
downloadxserver-3b265c59a6456f6e4abfb9e1694237bc56f1776a.tar.gz
glamor: Dump backtrace on GL error
Currrently, when a GL error is triggered, glamor would log the error which may not be sufficient to trace it back to the cause of the error. Also dump the backtrace which may give more information as to where the error comes from. Signed-off-by: Olivier Fourdan <ofourdan@redhat.com> Reviewed-by: Martin Peres <martin.peres@mupuf.org> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> https://gitlab.freedesktop.org/xorg/xserver/-/issues/1156
Diffstat (limited to 'glamor')
-rw-r--r--glamor/glamor.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/glamor/glamor.c b/glamor/glamor.c
index 3baef4b9f..b8406f42d 100644
--- a/glamor/glamor.c
+++ b/glamor/glamor.c
@@ -414,6 +414,7 @@ glamor_debug_output_callback(GLenum source,
LogMessageVerb(X_ERROR, 0, "glamor%d: GL error: %*s\n",
screen->myNum, length, message);
+ xorg_backtrace();
}
/**