mesa/src/gallium/drivers/rbug
Maarten Lankhorst f70c385351 gallium/build: Fix visibility CFLAGS in automake
v2: Andreas Boll <andreas.boll.dev@gmail.com>
    - Fix formatting - use one CFLAG per line

NOTE: This is a candidate for the 9.1 branch.

Signed-off-by: Maarten Lankhorst <m.b.lankhorst@gmail.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=59238
Reviewed-by: Andreas Boll <andreas.boll.dev@gmail.com>
2013-03-16 12:45:22 +01:00
..
Makefile.am gallium/build: Fix visibility CFLAGS in automake 2013-03-16 12:45:22 +01:00
rbug_context.c gallium: extend pipe_context::flush for it to accept an END_OF_FRAME flag 2013-01-04 13:18:33 +01:00
rbug_context.h rbug: update data structures, functions for future changes 2012-08-16 09:01:31 -06:00
rbug_core.c gallium: extend pipe_context::flush for it to accept an END_OF_FRAME flag 2013-01-04 13:18:33 +01:00
rbug_objects.c gallium: unify transfer functions 2012-10-11 21:12:16 +02: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 user_buffer_create from the interface 2012-05-12 23:13:45 +02: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>