• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

MakefileD22-Nov-2023179 139

READMED22-Nov-20231.1 KiB4525

SConscriptD22-Nov-2023214 1712

rbug_context.cD22-Nov-202340 KiB1,2371,015

rbug_context.hD22-Nov-20232.9 KiB10543

rbug_core.cD22-Nov-202325 KiB887656

rbug_objects.cD22-Nov-20237.2 KiB251169

rbug_objects.hD22-Nov-20235.5 KiB229154

rbug_public.hD22-Nov-20231.5 KiB419

rbug_screen.cD22-Nov-20239.5 KiB303223

rbug_screen.hD22-Nov-20232.9 KiB10150

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