• Home
  • History
  • Annotate
  • only in /external/mesa3d/src/gallium/drivers/rbug/
NameDateSize

..12-Mar-20154 KiB

Makefile12-Mar-2015179

rbug_context.c12-Mar-201540 KiB

rbug_context.h12-Mar-20152.9 KiB

rbug_core.c12-Mar-201525 KiB

rbug_objects.c12-Mar-20157.2 KiB

rbug_objects.h12-Mar-20155.5 KiB

rbug_public.h12-Mar-20151.5 KiB

rbug_screen.c12-Mar-20159.5 KiB

rbug_screen.h12-Mar-20152.9 KiB

README12-Mar-20151.1 KiB

SConscript12-Mar-2015214

README

1                              RBUG PIPE DRIVER
2
3
4= About =
5
6This directory contains a Gallium3D remote debugger pipe driver.
7It provides remote debugging functionality.
8
9
10= Usage =
11
12Do
13
14   GALLIUM_RBUG=true progs/trivial/tri
15
16which should open gallium remote debugging session. While the program is running
17you can launch the small remote debugging application from progs/rbug. More
18information is in that directory. Also for a gui see:
19
20   http://cgit.freedesktop.org/mesa/rbug-gui
21
22
23= Integrating =
24
25You can integrate the rbug pipe driver either inside the state tracker or the 
26target. The procedure on both cases is the same. Let's assume you have a 
27pipe_screen obtained by the usual means (variable and function names are just
28for illustration purposes):
29
30  real_screen = real_screen_create(...);
31
32The rbug screen is then created by doing
33
34  rbug_screen = rbug_screen_create(real_screen);
35
36You can then simply use rbug_screen instead of real_screen.
37
38You can create as many contexts you wish from rbug_screen::context_create they
39are automatically wrapped by rbug_screen.
40
41
42--
43Jose Fonseca <jrfonseca@tungstengraphics.com>
44Jakob Bornecrantz <jakob@vmware.com>
45