File: debugging.rst

package info (click to toggle)
mesa 25.3.2-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 322,268 kB
  • sloc: ansic: 2,212,173; xml: 1,032,268; cpp: 519,750; python: 81,988; asm: 40,568; yacc: 11,976; lisp: 5,067; lex: 3,452; sh: 1,049; makefile: 224
file content (17 lines) | stat: -rw-r--r-- 632 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
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 in DEBUG builds
(``--buildtype debug`` for Meson).

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/mesa/main/dlist.c`` for details.