20:25:34borodustjackdaniel: looks like ECL doesn't like if some foreign library starts its own native threads - i'm getting error like > Internal thread error in .. pthread_getspecific .. Did you forget to call `ecl_import_current_thread'?
20:26:20borodustthing is, it seems like i don't have access to those threads to do some initializations
20:27:09borodusti wonder though, why does ECL complain? i rechecked couple of times - i don't run lisp code in those threads (no callbacks passed)
21:13:56borodustmaybe it's something to do with a mishandled signal..
21:15:55borodustmaybe ECL tries to trap it but somehow handle it in the thread it doesn't know anything about
21:17:05borodustmy knowledge about signal handling is severely lacking ;p
21:58:39borodustyeh, looks like the actual problem is in memory misalignment (SIGBUS: illegal alignment), but ECL masks that
4:52:48screwtape`What's happening with ECL these days?
5:06:02jackdanielscrewtape`: what do you mean? it is ubder development
5:06:59jackdanielborodust: yes, signals. you either compile ecl w/o tgreading or you import each thread