[Bug 40423] Firefox GLX test crashes with Mesa 7.12-devel, Gallium 0.4 on AMD JUNIPER

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Aug 29 11:31:08 PDT 2011


https://bugs.freedesktop.org/show_bug.cgi?id=40423

--- Comment #4 from Ian Romanick <idr at freedesktop.org> 2011-08-29 11:31:07 PDT ---
(In reply to comment #3)
> (In reply to comment #3)
> > You can find the source code of this test here:
> > http://hg.mozilla.org/mozilla-central/file/d0700ba932b4/toolkit/xre/glxtest.cpp#l107
> 
> It has at least one obvious flaw: dlsym() can only be used to retrieve
> glXGetProcAddress(ARB) and the symbols defined by the Linux OpenGL ABI
> (basically OpenGL 1.2 + GL_ARB_multitexture). All other GL(X) symbols need to
> be retrieved with glXGetProcAddress(ARB).

That is kind of odd, but I don't think it's the problem.  The only GL symbol
that they use dlsym on is glGetString.  The library has to statically export
that. :)  glXQueryExtension, glXQueryVersion, glXCreatePixmap, glXMakeCurrent,
glXDestroyPixmap, and glXDestroyContext are in the same boat.

Technically speaking, glXChooseFBConfig, glXGetVisualFromFBConfig, and
glXCreateNewContext should be retrieved via glXGetProcAddress.  If dlsym
returns non-NULL, it seems unlikely to be a problem on our stack.  Since is
already done for glXBindTexImageEXT, it is a good idea to use glXGetProcAddress
for these functions as well.

> I didn't look further than that.
> 
> 
> > Unfortunately I don't have any more information about it: no stack, no more
> > device information.
> 
> Even assuming the crash wasn't due to a test bug, it'll be hard to do anything
> about it without that information.

I hacked up a stand-alone version, but I wasn't able to reproduce the crash on
the Intel drivers.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the dri-devel mailing list