Okay, on my Jaunty AMD64 I cannot replicate the problem even when I
switch to MESA software renderer (it doesn't occur with fglrx driver
either). However, looking through the tracebacks posted, it seems
pretty obvious that some configurations are failing when a call to
glGetError happens before the GL has a context. There's nothing in the
docs which says that should ever cause a failure (let alone a segfault),
so it seems we're looking at a broken implementation issue.
We could work around it by disabling GLUT error checking entirely, but
that seems a bit of a nuclear option, as it would change the API.
Instead I'm thinking we'll disable error checking *just* for the GLUT
functions commonly called before the GLUT context is created. I've
checked in changes to bzr head to implement this. Please do the
following and report whether the bug is fixed for you:
bzr branch lp:pyopengl
# add pyopengl/OpenGL to your PYTHONPATH
then run the test script.
--
Segmentation fault on amd64 in glutInitDisplayMode()
https://bugs.launchpad.net/bugs/289925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
