mesa/src/gallium/drivers/trace
Brian Paul 6d551f9ea3 trace: assorted whitespace and formatting fixes
Reviewed-by: Eduardo Lima Mitev <elima@igalia.com>
2016-02-19 08:49:51 -07:00
..
Makefile.am configure: Eliminate MSVC2008 compatibility. 2016-02-11 21:36:00 +00:00
Makefile.sources gallium/trace: ship all files in the tarball 2014-09-05 23:46:27 +01:00
README st/python: Remove bindings, and all its dependencies. 2011-04-06 08:26:04 +01:00
SConscript scons: Eliminate MSVC2008 compatibility. 2016-02-11 21:36:00 +00:00
tr_context.c trace: assorted whitespace and formatting fixes 2016-02-19 08:49:51 -07:00
tr_context.h gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
tr_dump.c gallium/drivers: Trivial code-style cleanup 2015-12-06 17:10:22 +01:00
tr_dump.h s/Tungsten Graphics/VMware/ 2014-01-17 20:00:32 +00:00
tr_dump_defines.h gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
tr_dump_state.c trace: add all compute related functions 2016-02-13 16:01:02 +01:00
tr_dump_state.h trace: add all compute related functions 2016-02-13 16:01:02 +01:00
tr_public.h trace: Add missing p_compiler.h include. 2015-06-12 12:14:11 +01:00
tr_screen.c trace: add all compute related functions 2016-02-13 16:01:02 +01:00
tr_screen.h s/Tungsten Graphics/VMware/ 2014-01-17 20:00:32 +00:00
tr_texture.c gallium/drivers: Trivial code-style cleanup 2015-12-06 17:10:22 +01:00
tr_texture.h gallium/drivers: Trivial code-style cleanup 2015-12-06 17:10:22 +01:00
trace.xsl trace: Re-license trace.xsl under MIT license. 2014-01-17 20:00:32 +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>