mesa/src/gallium/drivers/rbug
Marek Olšák 8db7dacf29 rbug: only add textures to the list
rbug-gui cannot display buffers, so it's pointless to add them.

Reviewed-by: Roland Scheidegger <sroland@vmware.com>
2014-08-19 12:20:18 +02:00
..
Makefile.am gallium/drivers: compact compiler flags into Automake.inc 2013-11-16 16:29:28 +00:00
Makefile.sources rbug: consolidate C sources list into Makefile.sources 2013-10-01 07:29:49 -07:00
rbug_context.c rbug: implement streamout context functions 2014-08-19 12:20:18 +02:00
rbug_context.h gallium/drivers: support more sampler views than samplers for more drivers 2013-11-28 04:01:54 +01:00
rbug_core.c rbug: send the actual number of layers to the client 2014-08-19 12:20:18 +02:00
rbug_objects.c rbug: only add textures to the list 2014-08-19 12:20:18 +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 swrast* (gallium, classic): add MESA_copy_sub_buffer support (v3) 2013-12-13 14:37:01 +10:00
rbug_screen.h rbug: Break out of trace 2010-05-12 20:15:23 +01:00
README s/Tungsten Graphics/VMware/ 2014-01-17 20:00:32 +00:00
SConscript rbug: consolidate C sources list into Makefile.sources 2013-10-01 07:29:49 -07: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 <jfonseca@vmware.com>
Jakob Bornecrantz <jakob@vmware.com>