[PATCH] Fix glFenceSync() retracing

José Fonseca jose.r.fonseca at gmail.com
Thu Jan 12 11:07:48 PST 2012


On Mon, Jan 9, 2012 at 9:23 PM, Ryan C. Gordon <icculus at icculus.org> wrote:
>
>> I see the problem, but unfortunately this change will break retracing
>> glFlushMappedBufferRange with a sub-range, and user memory pointers as
>> recorded by the virtual-address-regions branch (which tries to
>> reconstruct data in user arrays via mallocs and memcpys).
>
>
> I was worried there would be side effects like this. In the short term, it's
> not hard for me to use GL_NV_fence when tracing, so this isn't a big
> emergency for me; a better long-term solution in apitrace is the right
> decision, it was beyond my limited understanding of the codebase, though.

Could you provide me a trace where the problem happens? That would
help me a lot.

Jose


More information about the apitrace mailing list