Jose Fonseca <jfons...@vmware.com> writes: > ----- Original Message ----- >> Jordan Justen <jordan.l.jus...@intel.com> writes: >> >> > Motivated by wanting to see if GenTextures was called by an >> > application while debugging another Steam overlay issue. >> >> Making a systematic MESA_DEBUG=api using dispatch tables and code >> generation seems like it would be nice instead of adding it ad-hoc. Not >> something against this patch, just maybe a project for a janitor list if >> we have one. >> >> apitrace seems like it would be to replace it, but I've seen enough apps >> where it doesn't work (and in this case with the steam overlay it >> definitely doesn't) that we can't just rely on that. > > Could you elaborate on that? I'd like to understand how apitrace would miss > intercepting calls. > > A apart of some bug, the only explanation I can think of is calls done > inside Callists. If so then the only way to zoom in would be for > Apitrace to actually implement callists itself, and then inline > them. But this would have several side effects, and be too onerous for > a legacy feature.
Because apitrace isn't the only LD_PRELOAD libGL that people have done, and I think to get them to chain one has to know the other (and you probably want apitrace to be the last one before the GL).
pgpDomxK2hXE5.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
