Missing function calls?

José Fonseca jose.r.fonseca at gmail.com
Wed Sep 9 08:45:33 PDT 2015


Yes, a driver bug is unlikely.

A bug in your code is more likely.   Are you calling
`glEnableClientState(GL_VERTEX_ARRAY)` or `glEnableVertexAttribArray()` as
appropriate?

Jose

On Tue, Sep 8, 2015 at 7:50 PM, Mike Blumenkrantz <
michael.blumenkrantz at gmail.com> wrote:

> I am indeed not using VBOs, so the deferred calling is plausible I suppose.
>
> The curious thing here is that the reference implementation application
> uses the exact same function calls in the same order and they display
> normally in apitrace. Wouldn't a driver bug cause this application to also
> fail to display these function calls?
>
> On Tue, Sep 8, 2015 at 2:43 PM José Fonseca <jose.r.fonseca at gmail.com>
> wrote:
>
>> If you're not using VBOs, note that apitrace treats them specially:
>>
>>
>> https://github.com/apitrace/apitrace/blob/master/docs/BUGS.markdown#tracing
>>
>> If that's the case, from what you described, it sounds like apitrace
>> plans to defer the call, but it never does happen. This could be a bug in
>> the driver (they sometimes return bogus data on glGet* , causing apitrace
>> to go astray), or a bug in your on application (like not setting up VBOs
>> properly).
>>
>> Jose
>>
>>
>> On Tue, Sep 8, 2015 at 7:21 PM, Mike Blumenkrantz <
>> michael.blumenkrantz at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I'm working on a project using opengl on linux, and I turned to apitrace
>>> for debugging when I encountered a problem.
>>>
>>> According to apitrace, it seems that calls to glTexCoordPointer
>>> and glVertexPointer are "not happening"; they do not show up in the trace
>>> dumps anywhere. Using gdb, however, I can verify that both functions are at
>>> least calling into mesa/libGL as expected, even though apitrace is not
>>> catching them.
>>>
>>> Is it possible for gl calls to occur and not be picked up by apitrace?
>>> I've tested a similar/reference implementation of what I'm working on and
>>> both of these calls are displayed normally in the traces, so I'm wondering
>>> whether this is an issue in my app or apitrace.
>>>
>>> Thanks!
>>>
>>> _______________________________________________
>>> apitrace mailing list
>>> apitrace at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/apitrace
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20150909/651456da/attachment.html>


More information about the apitrace mailing list