On Tue, Oct 7, 2008 at 9:53 PM, josch <[EMAIL PROTECTED]> wrote: > > On Oct 7, 12:24 pm, "Alex Holkner" <[EMAIL PROTECTED]> wrote: >> Try to get a stack trace by running python in gdb > > like this? > > (gdb) run test.py > Starting program: /usr/bin/python test.py > [Thread debugging using libthread_db enabled] > [New Thread 0x7fa91ad216e0 (LWP 3250)] > [New Thread 0x411b7950 (LWP 3251)] > before label/image > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fa91ad216e0 (LWP 3250)] > 0x00007fa90e07cfa8 in ?? () from /usr/lib/libfontconfig.so.1 > (gdb) bt > #0 0x00007fa90e07cfa8 in ?? () from /usr/lib/libfontconfig.so.1
Great. Looks like fontconfig is the culprit -- or perhaps a GC issue at pyglet's end, triggered by the thread context switch -- seems unlikely, skimming through the code in pyglet/font/freetype.py. I'm running version of fontconfig 2.5.0 (`fc-match -V`). Can't really help beyond that, I'm afraid. A workaround may be to load all your fonts before starting threads. Alex. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
