[Mesa-dev] [PATCH] texobj: add verbose api trace messages to several routines

[Jose Fonseca]

----- 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.

There is also internal meta calls...

Jose