mesa/src/gallium/drivers/trace
2013-10-03 14:05:28 -06:00
..
Makefile.am trace: consolidate C sources list into Makefile.sources 2013-10-01 07:29:50 -07:00
Makefile.sources trace: consolidate C sources list into Makefile.sources 2013-10-01 07:29:50 -07:00
README st/python: Remove bindings, and all its dependencies. 2011-04-06 08:26:04 +01:00
SConscript trace: consolidate C sources list into Makefile.sources 2013-10-01 07:29:50 -07:00
tr_context.c trace: remove old bind_*_sampler_states() functions 2013-10-03 14:05:28 -06:00
tr_context.h trace: add context pointer sanity checking 2013-02-15 11:11:34 -07:00
tr_dump.c trace: Don't dump texture transfers. 2013-06-21 14:30:19 +01:00
tr_dump.h trace: Don't dump texture transfers. 2013-06-21 14:30:19 +01:00
tr_dump_state.c trace: Support bigger TGSI shaders. 2013-09-12 11:24:24 +01:00
tr_dump_state.h trace: Fix dumping of set_constant_buffer method. 2012-10-25 15:30:19 +01:00
tr_public.h rbug: Add to all targets that link against trace 2010-05-12 20:15:23 +01:00
tr_screen.c trace: Only close trace files on exit. 2013-04-25 14:18:33 +01:00
tr_screen.h trace: whitespace, comment clean-ups 2013-02-15 09:25:15 -07:00
tr_texture.c trace: add context pointer sanity checking 2013-02-15 11:11:34 -07:00
tr_texture.h trace: fix incorrect trace_surface::base.context pointer 2013-02-15 11:11:34 -07:00
trace.xsl trace: Number calls. 2009-03-25 21:04:05 +00:00

                             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>