From 8667d4d97a3e958a7f63c18c34a62469ba5d2079 Mon Sep 17 00:00:00 2001 From: ftrapero Date: Thu, 15 Jun 2017 14:15:08 +0200 Subject: Squashed 'nx-X11/extras/Mesa_6.4.1/' content from commit 53d1bc0 git-subtree-dir: nx-X11/extras/Mesa_6.4.1 git-subtree-split: 53d1bc081eb633aecbd5ab0bf3981f734a2102f2 --- docs/debugging.html | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 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 000000000..2df62f56e --- /dev/null +++ b/docs/debugging.html @@ -0,0 +1,38 @@ + + +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 v1.2.3