diff options
author | Brian Paul <[email protected]> | 2003-03-08 17:38:57 +0000 |
---|---|---|
committer | Brian Paul <[email protected]> | 2003-03-08 17:38:57 +0000 |
commit | 0b27aceae2464db3dd149cf4fd667e353a655c5e (patch) | |
tree | a8df88dd0893e04a6fe4f125ddd361a1bde9d7ae /docs/debugging.html | |
parent | dc32636cfd38916ad7b2150e10765026dbb64ce5 (diff) |
Documentation/website overhaul. The website content and doc/ directory
are now merged and are one and the same.
Diffstat (limited to 'docs/debugging.html')
-rw-r--r-- | docs/debugging.html | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/docs/debugging.html b/docs/debugging.html new file mode 100644 index 00000000000..cdefa7d210d --- /dev/null +++ b/docs/debugging.html @@ -0,0 +1,36 @@ +<HTML> + +<TITLE>Debugging Tips</TITLE> + +<BODY text="#000000" bgcolor="#55bbff" link="#111188"> + +<H1>Debugging Tips</H1> + +<p> + Normally Mesa (and OpenGL) records but does not notify the user of + errors. It is up to the application to call + <code>glGetError</code> 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. +</p> + +<p> + 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. +</p> +<p> + In your debugger you can set a breakpoint in _mesa_error() to trap Mesa + errors. +</p> +<p> + There is a display list printing/debugging facility. See the end of + src/dlist.c for details. +</p> + +</BODY> +</HTML> |