Bug#528708: Not completely fixed upstream in 7.4.2
On Wed, 2009-05-20 at 11:00 -0700, Daniel Schepler wrote:
> On Wednesday 20 May 2009 01:15:51 Michel Dänzer wrote:
> > On Tue, 2009-05-19 at 17:01 -0700, Daniel Schepler wrote:
> > > But with the application I'm developing I still get the condition where
> > > glGetString(GL_VERSION) returns NULL in my override of
> > > QGLWidget::initializeGL.
> >
> > Is a GLX context current when you call glGetString?
>
> Yes, as I said in the original post, QGLWidget::initializeGL is called with
> its GL context already made current. And just to verify that, I tried adding
> an explicit call to QGLWidget::makeCurrent at the start of my override, which
> didn't help. Then, I added some debugging code to switch to another (shared)
> context and back, printing the return value of glXGetCurrentContext after each
> switch and before the first one. That inexplicably made the glGetString call
> start working, although the context values looked like they were doing the
> right thing.
>
> And with the original code, running the program with MESA_DEBUG=1 makes the
> library complain about calling glGetString with no active context, even when a
> debugging glXGetCurrentContext shows the correct (nonzero) value.
Weird. Please report this upstream at http://bugs.freedesktop.org ,
product Mesa, component Mesa core. Preferably with a small test program
which exhibits the problem.
--
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
Reply to: