diff options
| author | José Fonseca <jose.r.fonseca@gmail.com> | 2011-04-04 11:41:30 +0100 |
|---|---|---|
| committer | José Fonseca <jose.r.fonseca@gmail.com> | 2011-04-06 08:26:04 +0100 |
| commit | afeaf1771d0ccbd2482c5ad7fa237c50b4d3921e (patch) | |
| tree | fe9bc95a17168a8de07a207a1383f41d27274c95 /src/gallium/drivers/trace/README | |
| parent | 14b574433c7faedaa18f1c946159cb03630c7d9f (diff) | |
| download | external_mesa3d-afeaf1771d0ccbd2482c5ad7fa237c50b4d3921e.zip external_mesa3d-afeaf1771d0ccbd2482c5ad7fa237c50b4d3921e.tar.gz external_mesa3d-afeaf1771d0ccbd2482c5ad7fa237c50b4d3921e.tar.bz2 | |
st/python: Remove bindings, and all its dependencies.
Because:
- bindings are not fully automatic, and they are broken most of the time
- unit tests/samples can be written in C on top of graw
- tracing/retracing is more useful at API levels with stable ABIs such as
GL, producing traces that cover more layers of the driver stack and and
can be used for regression testing
Diffstat (limited to 'src/gallium/drivers/trace/README')
| -rw-r--r-- | src/gallium/drivers/trace/README | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/src/gallium/drivers/trace/README b/src/gallium/drivers/trace/README index c210cba..cacd2e1 100644 --- a/src/gallium/drivers/trace/README +++ b/src/gallium/drivers/trace/README @@ -13,12 +13,17 @@ It can traces all incoming calls. For tracing then do - GALLIUM_TRACE=tri.trace progs/trivial/tri + GALLIUM_TRACE=tri.trace trivial/tri which should create a tri.trace file, which is an XML file. You can view copying trace.xsl to the same directory, and opening with a XSLT capable browser such as Firefox or Internet Explorer. +For long traces you can use the + + src/gallium/tools/trace/dump.py tri.trace | less -R + + == Remote debugging == For remote debugging see: |