profiling doesn't seem to work
io.github.apitrace at io7m.com
io.github.apitrace at io7m.com
Sat Aug 2 03:15:21 PDT 2014
'Lo.
I'm having issues getting profiling in qapitrace to work at all. I'm
guessing this is a symptom of another problem as although I can step
through a trace in qapitrace and see how framebuffers, texture states,
shaders, etc, change over time (in the "Current state" panel on the
right), the actual window that pops up to show the replay is always
black (or contains garbage as if the window has never been cleared).
When attempting to profile any trace, I get "Process exited with
non-zero exit code" in the status bar at the bottom of the main window
and the profiling results are always blank.
Any idea what could be causing this, or how I could find out what's
going wrong?
System is:
Linux viper 3.15.5-2-ARCH #1 SMP PREEMPT Fri Jul 11 07:56:02 CEST
2014 x86_64 GNU/Linux
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.4
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 3.0 Mesa 10.2.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES
3.0
Apitrace is the current git head
71f5a35e3bc1801847413cff1f14fc3b5cd991ca.
Here's a trace I use (any trace has the same results, apparently):
http://waste.io7m.com/2014/08/02/viewer_STranslucent1_deferred_20140802_094500
M
More information about the apitrace
mailing list