[Mesa-dev] [PATCH] texobj: add verbose api trace messages to several routines
eric at anholt.net
Wed Feb 27 08:53:21 PST 2013
Jose Fonseca <jfonseca at vmware.com> writes:
> ----- Original Message -----
>> Jordan Justen <jordan.l.justen at 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).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the mesa-dev