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 -~----------~----~----~----~------~----~------~--~---
