On Thu, Mar 5, 2009 at 10:57 AM, Richard Thomas <[email protected]> wrote: > > I am experiencing a very weird bug. My interpreter keeps segfaulting > when I do any serious amount of GL. It almost always happens but not > after a consistent amount of time. I have a simple lap timer program I > wrote and to keep it from being boring I put a little expanding > circles effect in the background. Now if I disable the label that's > displaying the time or the circles then it'll run seemingly forever > without crashing, if I do both at once it crashes within a minute or > so. > > I've exhausted almost every possibility I can think of. I ran memtest > for half a dozen passes in cases I had a hardware fault. Pyglet's GL > wrapper is simple enough that I can't really see ctypes being the > problem or foreign function libraries would be giving up all over the > place. Besides which nobody else I've tried has had this problem. > > Is there anyone who's experienced anything like this? > > Sometimes I get a bus error instead of a seg fault. > > Richard. > > >
You can find where the segfault is happening by getting a stack trace in GDB. Try: $ gdb python (gdb) run <program>.py This should show which library the segfault occurred in. Pyglet uses more libraries than just OpenGL (certain fontconfig versions seem to cause problems, for instance), so hopefully you can narrow it down with one of those. Post your stack trace when you have it... Colin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
