Home | History | Annotate | only in /external/mesa3d/src/gallium/drivers/rbug
Up to higher level directory
NameDateSize
Makefile20-Jun-2014179
rbug_context.c20-Jun-201440K
rbug_context.h20-Jun-20142.9K
rbug_core.c20-Jun-201425K
rbug_objects.c20-Jun-20147.2K
rbug_objects.h20-Jun-20145.5K
rbug_public.h20-Jun-20141.5K
rbug_screen.c20-Jun-20149.5K
rbug_screen.h20-Jun-20142.9K
README20-Jun-20141.1K
SConscript20-Jun-2014214

README

      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 <jrfonseca (a] tungstengraphics.com>
     44 Jakob Bornecrantz <jakob (a] vmware.com>
     45