https://bugs.freedesktop.org/show_bug.cgi?id=47166
--- Comment #3 from José Fonseca <jfons...@vmware.com> 2012-03-15 10:05:58 PDT
---
(In reply to comment #2)
> Is there a secret to getting apitrace to work with OSMesa? Since I'm using
> either OSMesaGetProcAddress or dlopen("libOSMesa.so",...)/dlsym(...) to get
> the
> extension function pointers, they do not get logged by apitrace which only
> redirects calls to libGL.so. If you want, I can give you a trace that doesn't
> have the extension function calls logged, but that doesn't seem like it will
> give you what you need to reproduce the problem since so many extension
> function calls are being used.
apitrace doesn't support OSMesa, and it would require some work to support it.
Before that, it would be better to recode the application using a standard
OpenGL implement, and see if that allows to reproduce the problem when
retracing on Mesa.
apitrace works on windows too. You can also try to trace with AMD/NVIDIA
drivers on Windows.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
