From 2702c90d7a39fca2a3319c5e915fd290cb31fc70 Mon Sep 17 00:00:00 2001 From: Radosław Kujawa Date: Fri, 17 Jul 2026 14:54:32 +0200 Subject: Initial import. --- docs/debugging.html | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 docs/debugging.html (limited to 'docs/debugging.html') diff --git a/docs/debugging.html b/docs/debugging.html new file mode 100644 index 0000000..cdefa7d --- /dev/null +++ b/docs/debugging.html @@ -0,0 +1,36 @@ + + +Debugging Tips + + + +

Debugging Tips

+ +

+ Normally Mesa (and OpenGL) records but does not notify the user of + errors. It is up to the application to call + glGetError to check for errors. Mesa supports an + environment variable, MESA_DEBUG, to help with debugging. If + MESA_DEBUG is defined, a message will be printed to stdout whenever + an error occurs. +

+ +

+ More extensive error checking is done when Mesa is compiled with the + DEBUG symbol defined. You'll have to edit the Make-config file and + add -DDEBUG to the CFLAGS line for your system configuration. You may + also want to replace any optimization flags with the -g flag so you can + use your debugger. After you've edited Make-config type 'make clean' + before recompiling. +

+ In your debugger you can set a breakpoint in _mesa_error() to trap Mesa + errors. +

+ There is a display list printing/debugging facility. See the end of + src/dlist.c for details. +

+ + + -- cgit