Yeap, I tried a program where a context was created and glGetError() was called and it worked fine. The reason I tried this was because when I call gl.glGetError inside of the python code I also got a segmentation fault. Now it makes sense since the context was never made current. I see that the pyglet checks to see if there was opengl errors automatically. Now i'm very confused, because glMakeCurrent returned zero, but glGetError did not detect anything. Anything else I can do?
On Fri, May 29, 2009 at 11:26 PM, Tristam MacDonald <[email protected]>wrote: > On Fri, May 29, 2009 at 11:18 PM, Shawn Krisman > <[email protected]>wrote: > >> The problem seems to run alot deeper than pyglet, probably as expected. >> This guy: >> >> #include <GL/glx.h> >> #include <GL/gl.h> >> >> int main(int argc, char* argv[]) { >> glGetError(); >> return 0; >> } >> >> causes a segmentation fault on my computer. I feel like the issue is >> related to drivers, but i'm not sure who to write a bug report too. >> > That particular program is all but guaranteed to segfault. No OpenGL > functions are allowed to be called until a valid context is made current. > > -- > Tristam MacDonald > http://swiftcoder.wordpress.com/ > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
