Ok so it definetly was related to the -O2 optimization setting. After seriously debugging the problem, its still very unclear what happened. All of these problems stem from the x11 server. On the client side the errors are in a function called process_events. The error are stored in a xError struct, which stores its errors as integers that I can't totally decode without some guessing. My best guess as to the error is a BadMatch Error. So like I stated before glXMakeCurrent was last in a long line of errors given by the code. The first was actually in a call XInternAtom. Interestingly the call succeeds but the error is still raised. Which error is still a bit of a mystery to me. Why it raises the error though is the real mystery. Another smaller mystery is why the XErrorHandler isn't handling these errors.
On Mon, Jun 1, 2009 at 4:18 AM, Tristam MacDonald<[email protected]> wrote: > On Mon, Jun 1, 2009 at 5:47 AM, Alex Holkner <[email protected]> wrote: >> >> On 01/06/2009, at 5:05 PM, Shawn Krisman <[email protected]> >> wrote: >> >> > So I compiled a debug version of the glx libraries to really find out >> > what was going on. The results where ridiculously strange. First I >> > have never seen anything like this in gdb. It looked some of the code >> > was just randomly going back a few instructions every once in a while. >> > Except not randomly because every time I went through the debugger it >> > moved in the same way every time, very very strange. I should also >> > note that gdb didn't say anything about switching functions or >> > threads. Also important to note is that when it moves back it also >> > resets to the state it was before the newer instructions. >> >> Sounds like you had optimisation flags enabled when you compiled the >> library. > > > That could also be either exception handling (if C++), or the related C > construct using setjmp/longjmp. > -- > 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 -~----------~----~----~----~------~----~------~--~---
