Index of /archives/NetBSD/NetBSD-release-9/xsrc/external/mit/MesaLib.old/dist/src/gallium/drivers/rbug
Name Last modified Size Description
![[PARENTDIR]](/icons/back.gif)
Parent Directory -
![[DIR]](/icons/folder.gif)
CVS/ 2020-03-20 07:39 -
![[TXT]](/icons/text.gif)
Makefile.am 2019-03-08 19:19 1.3K
Makefile.in 2019-03-08 19:19 25K
![[ ]](/icons/unknown.gif)
Makefile.sources 2019-03-08 19:19 81
README 2019-03-08 19:19 1.1K
SConscript 2019-03-08 19:19 188
rbug_context.c 2019-03-08 19:19 41K
rbug_context.h 2019-03-08 19:19 2.9K
rbug_core.c 2019-03-08 19:19 25K
rbug_objects.c 2019-03-08 19:19 7.2K
rbug_objects.h 2019-03-08 19:19 5.5K
rbug_public.h 2019-03-08 19:19 1.5K
rbug_screen.c 2019-03-08 19:19 9.5K
rbug_screen.h 2019-03-08 19:19 2.9K
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>