Cross Reference: /external/chromium_org/third_party/mesa/src/src/gallium/drivers/trace/

                             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/drivers/rbug/README


= Integrating =

You can integrate the trace pipe driver either inside the state tracker 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>
Name	Date	Size
..	12-Mar-2015	4 KiB
Makefile	12-Mar-2015	191
README	12-Mar-2015	1.3 KiB
SConscript	12-Mar-2015	271
tr_context.c	12-Mar-2015	45.5 KiB
tr_context.h	12-Mar-2015	1.9 KiB
tr_dump.c	12-Mar-2015	12.3 KiB
tr_dump.h	12-Mar-2015	5.5 KiB
tr_dump_state.c	12-Mar-2015	18.7 KiB
tr_dump_state.h	12-Mar-2015	3.2 KiB
tr_public.h	12-Mar-2015	1.6 KiB
tr_screen.c	12-Mar-2015	13.1 KiB
tr_screen.h	12-Mar-2015	2 KiB
tr_texture.c	12-Mar-2015	4.2 KiB
tr_texture.h	12-Mar-2015	3.5 KiB
trace.xsl	12-Mar-2015	4.2 KiB