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

..09-Feb-2022-

READMEH A D09-Feb-20221.1 KiB4525

rbug_context.cH A D09-Feb-202245 KiB1,3761,139

rbug_context.hH A D09-Feb-20222.9 KiB10543

rbug_core.cH A D09-Feb-202224.5 KiB888658

rbug_objects.cH A D09-Feb-20227.3 KiB255172

rbug_objects.hH A D09-Feb-20225.5 KiB229154

rbug_public.hH A D09-Feb-20221.6 KiB4915

rbug_screen.cH A D09-Feb-202216.8 KiB497390

rbug_screen.hH A D09-Feb-20222.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 gallium frontend 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 <jfonseca@vmware.com>
44Jakob Bornecrantz <jakob@vmware.com>
45