----- Original Message ----- > On Wed, Feb 6, 2013 at 4:30 PM, Kristian Høgsberg <k...@bitplanet.net> > wrote: > > On Tue, Feb 5, 2013 at 8:43 AM, <jfons...@vmware.com> wrote: > >> From: José Fonseca <jfons...@vmware.com> > >> > >> I'd like to test Mesa OpenGL ES along side with NVIDIA libGL > >> drivers. But > >> without this change, I get a NULL pointer dereference. > > > > Which DRI driver doesn't support the flush extension? EGL is > > expected > > to flush before swap buffer (and we can't rely on glFLush since > > that > > may be optimized to not do anything) so we have to have this DRI > > driver entry point. The EGL DRI loader shouldn't load a DRI driver > > that doesn't support the flush extension in the first place, of > > course.
I was using EGL GLES swrast, but on a system with proprietary NVIDIA drivers installed. > And looking at the code, the EGL DRI2 loader doesn't load drivers > that > doesn't have the flush extension, so it sounds like the driver in > question claims is supports the extension, but passes an extension > struct with a NULL pointer in the flush function pointer. I'm not very familiar with the code. Is there any place I can break point to determine whether this is being (wrongly) advertised or not? Jose _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev