On Mon, Jun 1, 2009 at 12:52 AM, Tristam MacDonald <[email protected]> wrote: > On Sun, May 31, 2009 at 7:56 AM, Shawn Krisman <[email protected]> > wrote: >> >> Correction switching to mesa 3d libraries without dri acceleration and >> glx support will cause this segmentation fault (more specifically the >> ubuntu libgl1-mesa-swx11 package.) Without glx and dri, pyglet because >> unuseable so this is still a very big bug. I got the newest dri >> enabled libraries and we still have the bug albeit without so many >> segmentation fault issues. So as far as I know the problem stems from >> glXMakeCurrent, it returns false. This page shows that there are a >> number of ways this call can fail: >> >> http://www.opengl.org/documentation/specs/man_pages/hardcopy/GL/html/glx/xmakecurrent.html. >> Unfortunately my belief is that that errors are stored in the same >> queue that is queried by glGetError. This is unfortunate because the >> actions of glGetError are undefined until a context is made current, >> meaning that there seems to be know way to find out why this device >> context is actually failing. > > The glx errors should be in the Xlib error queue, not the OpenGL error > queue. Have you tried installing an X error handler? > Instructions on how to do so can be found > here: http://www.motifdeveloper.com/tips/tip29.html
pyglet installs an Xlib error handler by default. See pyglet/window/xlib/__init__.py Alex. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
