src/gallium/drivers/trace/README

   1                              TRACE PIPE DRIVER
   2
   3
   4 = About =
   5
   6 This directory contains a Gallium3D trace debugger pipe driver.
   7 It can traces all incoming calls.
   8
   9
  10 = Usage =
  11
  12 == Tracing ==
  13
  14 For tracing then do
  15
  16  GALLIUM_TRACE=tri.trace progs/trivial/tri
  17
  18 which should create a tri.trace file, which is an XML file. You can view copying
  19 trace.xsl to the same directory, and opening with a XSLT capable browser such as
  20 Firefox or Internet Explorer.
  21
  22 == Remote debugging ==
  23
  24 For remote debugging see:
  25
  26   src/gallium/drivers/rbug/README
  27
  28
  29 = Integrating =
  30
  31 You can integrate the trace pipe driver either inside the state tracker or the
  32 target. The procedure on both cases is the same. Let's assume you have a
  33 pipe_screen obtained by the usual means (variable and function names are just
  34 for illustration purposes):
  35
  36   real_screen = real_screen_create(...);
  37
  38 The trace screen is then created by doing
  39
  40   trace_screen = trace_screen_create(real_screen);
  41
  42 You can then simply use trace_screen instead of real_screen.
  43
  44 You can create as many contexts you wish from trace_screen::context_create they
  45 are automatically wrapped by trace_screen.
  46
  47
  48 --
  49 Jose Fonseca <jfonseca@vmware.com>
  50 Jakob Bornecrantz <jakob@vmware.com>