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