4 (in no particular order)
10 * Allow clamping to a GL version or a number of extensions.
12 * Trace multiple threads:
14 * `GetCurrentThreadId()`
18 * Put zlib (de)compression in a separate thread.
22 * Trace window sizes somehow
24 * Allow to distinguish between the calls really done by the program, vs the
25 fakes one necessary to retrace correctly.
27 * Start tracing on demand (e.g., key-press, or by frame no), emitting calls
28 that recreate all current state.
30 * Add option to include call stack frames in the trace.
32 * Trace the internal GL calls done by GLU on Mac OS X & Windows.
38 * Use visuals that best match those used in the trace; specially auto
39 detect single/double buffer visuals.
41 * Respect multiple context sharing of the traces.
43 * Support multiple threads
45 * Leverage `ARB_debug_output` where available.
55 * Visualize meshes in draw commands.
57 * Breakpointing and step-by-step debugging.
62 * Add retrace Replay all the calls in a trace
63 * Add trim Trim a trace by including only the specified calls/frames
64 * Add dump-state Output the OpenGL state in JSON format
65 * Add dump-images Create image files for each frame/drawing operation of a trace
67 * Add some common command-line options:
69 Most commands acting on a trace accept the following common options:
71 --calls=[RANGE] Operate only on calls with index numbers within
74 --frames=[RANGE] Operate only on frames with index numbers within
77 --functions=[REGEXP] Operate only on function calls which have a
78 name that matches the given regular expression.
80 A [RANGE] can be any of the following:
84 4 A single number specifying a single call or frame.
86 10-20 Two numbers separated by '-' (FIRST-LAST) specifying a
87 range of consecutive calls/frames from FIRST to LAST. If
88 either of FIRST or LAST is omitted, the first or last
89 call/frame index in the trace will be used.
91 1-100/5 Either of the above range specifications followed by '/'
92 and a number (INTERVAL). This specifies the inclusion of
93 only each INTERVAL call/frame within the range. For
94 example, 1-100/5 species frame 1, frame 5, frame 10,
97 4,10-20/2 A comma separated list of any of the above range
98 specifications, specifying the union of the ranges.
100 * Add some retrace-specific options (-b, -db, -sb, -v)
102 * Add some trime-specific options (--every={draw,framebuffer,frame})
104 * Accept a filename for --calls or --functions (to use the same calls
105 or functions as present in a trace dump).
107 * Add an "apitrace bisect" for trimming down a trace based on user
110 * Add an "apitrace git-bisect-helper" for calling from git-bisect.
116 * Side-by-side trace diffing; either as a separate tool on or the GUI.
118 * Ability to extract just a single frame from a trace, and all previous calls
119 that contributed to it:
121 * via a state tracker (i.e., knowledge of how calls affect the state);
123 * or by leveragine retrace, dumping the calls to emit all state at beginning
129 * open issues on [github](https://github.com/apitrace/apitrace/issues)
131 * _Known issues_ section in BUGS.markdown
133 * FIXME, TODO, and XXX comments on the source code.