OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add more more code-tags

Browse Source 
It's easier to read function-names, file-names and other
"machine"-related strings if they are formatted in a monospace font. So
let's mark these up with code-tags.

Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
This commit is contained in:
Erik Faye-Lund
2019-05-28 13:14:03 +02:00
parent 0ee366960c
commit 392c083377
6 changed files with 50 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/debugging.html
View File

@@ -20,9 +20,9 @@
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.
environment variable, <code>MESA_DEBUG</code>, to help with debugging. If
<code>MESA_DEBUG</code> is defined, a message will be printed to stdout
whenever an error occurs.
</p>
<p>
@@ -30,12 +30,12 @@
(<code>--buildtype debug</code> for meson, <code>build=debug</code> for scons).
</p>
<p>
In your debugger you can set a breakpoint in _mesa_error() to trap Mesa
errors.
In your debugger you can set a breakpoint in <code>_mesa_error()</code> to trap
Mesa errors.
</p>
<p>
There is a display list printing/debugging facility. See the end of
src/dlist.c for details.
<code>src/dlist.c</code> for details.
</p>
</div>