Index of /archives/NetBSD/NetBSD-release-10/xsrc/external/mit/MesaLib/dist/src/gallium/auxiliary/driver_trace
Name Last modified Size Description
![[PARENTDIR]](/icons/back.gif)
Parent Directory -
![[DIR]](/icons/folder.gif)
CVS/ 2022-12-18 05:57 -
![[TXT]](/icons/text.gif)
README 2022-05-09 10:23 1.3K
tr_context.c 2022-05-09 10:23 68K
tr_context.h 2022-05-09 10:23 2.7K
tr_dump.c 2022-05-09 10:27 13K
tr_dump.h 2022-05-09 10:23 5.8K
tr_dump_defines.h 2022-05-09 10:23 1.8K
tr_dump_state.c 2022-05-09 10:23 29K
tr_dump_state.h 2022-05-09 10:23 4.0K
tr_public.h 2022-05-09 10:23 1.6K
tr_screen.c 2022-05-09 10:23 34K
tr_screen.h 2022-05-09 10:23 2.0K
tr_texture.c 2022-05-09 10:23 3.4K
tr_texture.h 2022-05-09 10:23 3.0K
![[ ]](/icons/unknown.gif)
trace.xsl 2019-03-10 12:42 4.6K
TRACE PIPE DRIVER
= About =
This directory contains a Gallium3D trace debugger pipe driver.
It can traces all incoming calls.
= Usage =
== Tracing ==
For tracing then do
GALLIUM_TRACE=tri.trace trivial/tri
which should create a tri.trace file, which is an XML file. You can view copying
trace.xsl to the same directory, and opening with a XSLT capable browser such as
Firefox or Internet Explorer.
For long traces you can use the
src/gallium/tools/trace/dump.py tri.trace | less -R
== Remote debugging ==
For remote debugging see:
src/gallium/auxiliary/driver_rbug/README
= Integrating =
You can integrate the trace pipe driver either inside the gallium frontend or the
target. The procedure on both cases is the same. Let's assume you have a
pipe_screen obtained by the usual means (variable and function names are just
for illustration purposes):
real_screen = real_screen_create(...);
The trace screen is then created by doing
trace_screen = trace_screen_create(real_screen);
You can then simply use trace_screen instead of real_screen.
You can create as many contexts you wish from trace_screen::context_create they
are automatically wrapped by trace_screen.
--
Jose Fonseca <jfonseca@vmware.com>
Jakob Bornecrantz <jakob@vmware.com>