On Sat, Jun 4, 2016 at 3:44 PM, Ilia Mirkin wrote:
> On Sat, Jun 4, 2016 at 3:36 PM, Ian Romanick wrote:
>> How about if you give me a chance to actually fix the problem instead of
>> papering over it?
>
> That sounds fine too. It's causing real problems for debugging right
> now though (glretrac
On Sat, Jun 4, 2016 at 3:36 PM, Ian Romanick wrote:
> How about if you give me a chance to actually fix the problem instead of
> papering over it?
That sounds fine too. It's causing real problems for debugging right
now though (glretrace creates debug contexts by default), which is why
I wanted t
How about if you give me a chance to actually fix the problem instead of
papering over it?
On June 4, 2016 10:17:59 AM Ilia Mirkin wrote:
This is causing problems with glretrace and various traces I've seen,
including F1 2015 and PCSX2. I haven't carefully debugged what's going
on, but the g
