Looking more carefully, this is a bit weird... The pthread_getspecific call seems to be failing, which makes it seem that the call that created the corresponding key has not been called (can you check that?). Even that shouldn't be causing a crash here. This doesn't look like it's anywhere near any LanguageKit code, so my guess is some memory corruption elsewhere (possibly due to LanguageKit).
Can you try running it in valgrind and seeing if you can find some invalid writes? David On 11 Dec 2010, at 05:37, Christopher Armstrong wrote: > #0 0xb6f40ed0 in pthread_getspecific () from /lib/i686/cmov/libpthread.so.0 > #1 0xb78c3034 in GSCurrentThread () at NSThread.m:344 > #2 0xb77ad63d in +[NSAutoreleasePool addObject:] (self=0xb7a50500, > _cmd=0xb7a7cf48, anObj=0x8ec31e8) at NSAutoreleasePool.m:232 > #3 0xb7855ba7 in -[NSObject autorelease] (self=0x8ec31e8, _cmd=0xb5854660) > at NSObject.m:1601 > #4 0xb58547f7 in ?? () > #5 0x08ec31e8 in ?? () > #6 0xb5854660 in ?? () > #7 0xb77ad624 in +[NSAutoreleasePool currentPool] (self=0x8ec31e8, > _cmd=0xb5854678) at NSAutoreleasePool.m:228 -- This email complies with ISO 3103 _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
