Detect and Compile?

[José Fonseca]

On Tue, Mar 12, 2013 at 8:21 AM, Alexander Monakov <amonakov at ispras.ru>wrote:

>
>
> On Tue, 12 Mar 2013, Shuang He wrote:
>
> > Hi,
> >     Just realized that apitrace may affect code path of 3D application,
> since
> > 3D application may try different ways to probe for supported GL
> extension. One
> > way would be dlsym()
>
> Such application would be ignoring the OpenGL ABI.
>
> In any case, such application must consult extension strings before
> actually
> using the functions it obtained via dlsym, otherwise it has no possible
> way of
> knowing if they will actually work.
>

Precisely.


> But yes, the world is not perfect, and there are applications that probe
> libGL
> with dlsym and also ignore extension strings.
>

Apps that make such mistake may indeed exist, but I believe they must be
relatively rare as they would break in so many cases other than apitrace,
as having more symbols than supported entrypoints is quite common (Mesa
drivers, indirect GLX, MacOSX, etc).  So I don't see a reason to go out of
our way to cater for them.  If/when such app appears, then my suggestion
would be to make a custom build of apitrace that hid any symbol that was
confusing the app.

Jose
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20130312/fff5b833/attachment.html>