| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2009-03-25 | python: Use a sequential number to identify each call. | José Fonseca | |
| TODO: Modify the trace driver to generate these on the XML file itself. | |||
| 2009-03-25 | python/trace: Control the interpreter from command line options. | José Fonseca | |
| 2008-11-19 | python/retrace: Highlight the trace dump to help to visualize. | José Fonseca | |
| 2008-11-19 | python/retrace: Use the usual BSD-style license. | José Fonseca | |
| 2008-08-22 | python/retrace: Process the trace call-by-call (instead of reading ↵ | José Fonseca | |
| everything into memory). | |||
| 2008-08-21 | python/retrace: Support gziped traces. | José Fonseca | |
| 2008-08-19 | python/retrace: Trim null chars. | José Fonseca | |
| They are often left in memory mapped files, and are not part of the XML accept chars anyway. | |||
| 2008-08-15 | python/retrace: Keep addresses as strings. | José Fonseca | |
| To simplify looking up these in the trace. | |||
| 2008-08-14 | python/retrace: Application capable of replaying gallium traces. | José Fonseca | |
| At the moment it is capable of replaying trivial/tri kind of apps. See README for status. | |||
