mesa/src/gallium/drivers/rbug
Jakob Bornecrantz 07838ff990 rbug: Use the call mutex
Fixes crashes in [soft|llvm]pipe when replacing shaders
2011-03-13 18:13:55 +01:00
..
Makefile rbug: Break out of trace 2010-05-12 20:15:23 +01:00
rbug_context.c rbug: Use the call mutex 2011-03-13 18:13:55 +01:00
rbug_context.h rbug: Fix draw blocking 2010-05-12 20:15:23 +01:00
rbug_core.c gallium: remove flags from the flush function 2011-03-11 21:39:31 +01:00
rbug_objects.c rbug: Fix surface reference leak 2011-01-25 00:58:46 +01:00
rbug_objects.h gallium: support for array textures and related changes 2010-12-02 04:33:43 +01:00
rbug_public.h rbug: Add to all targets that link against trace 2010-05-12 20:15:23 +01:00
rbug_screen.c gallium: remove the geom_flags param from is_format_supported 2011-03-11 21:39:30 +01:00
rbug_screen.h rbug: Break out of trace 2010-05-12 20:15:23 +01:00
README scons: Revamp how to specify targets to build. 2010-11-01 13:30:22 +00:00
SConscript scons: Add aliases for several pipe drivers. 2010-11-02 12:35:52 +00:00

                              RBUG PIPE DRIVER


= About =

This directory contains a Gallium3D remote debugger pipe driver.
It provides remote debugging functionality.


= Usage =

Do

   GALLIUM_RBUG=true progs/trivial/tri

which should open gallium remote debugging session. While the program is running
you can launch the small remote debugging application from progs/rbug. More
information is in that directory. Also for a gui see:

   http://cgit.freedesktop.org/mesa/rbug-gui


= Integrating =

You can integrate the rbug pipe driver either inside the state tracker or the 
target. The procedure on both cases is the same. Let's assume you have a 
pipe_screen obtained by the usual means (variable and function names are just
for illustration purposes):

  real_screen = real_screen_create(...);

The rbug screen is then created by doing

  rbug_screen = rbug_screen_create(real_screen);

You can then simply use rbug_screen instead of real_screen.

You can create as many contexts you wish from rbug_screen::context_create they
are automatically wrapped by rbug_screen.


--
Jose Fonseca <jrfonseca@tungstengraphics.com>
Jakob Bornecrantz <jakob@vmware.com>