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.
On Fri, May 29, 2009 at 6:42 PM, Shawn Krisman <[email protected]>wrote:
> Cool I made it through the source and I found something! So the context is
> created ok, but a call to glXMakeCurrent fails. This is found on line 777 of
> window/xlib/__init__.py. The reason it still goes through is because the
> code around that area completely lacks error checking. I was difficult for
> me to find any information about the error but I did end up finding about
> c_types.get_errno() which returned the number 0. Either this is really
> profound or, most likely, it just shows that this new method is kind of
> sucking. If anyone has any ideas about how I can move forward on trying to
> figure out more about how this failed it would be greatly appreciated. Also
> I will be on irc all day under the name telaviv
>
>
> On Fri, May 29, 2009 at 7:40 AM, Tristam MacDonald
> <[email protected]>wrote:
>
>> On Thu, May 28, 2009 at 10:15 PM, krisman.shawn
>> <[email protected]>wrote:
>>
>>>
>>> Same issue here! Here is my backtrace after running window.Window()
>>
>>
>>
>> ...
>>
>>
>> That looks as if glGetString() is being called before the context is
>> created - might want to go through the source to make sure it isn't.
>>
>> --
>> 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
-~----------~----~----~----~------~----~------~--~---
