state of --with-threads=POSIX_THREADS?
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <9594accee7cd49b7873efb1848d4d7b8@HE105658.emea1.cds.t-internal.com> |
Hi, What's the state of threads in the current clisp? Is it a release target? Is it worth opening bug reports about it? On my 32 bit OSX 10.6.8 machine, and in my environment (no ffcall, no sigsegv library!), all the regular build-porting-gcc-* expected to build (i.e. not the debug one, not the gen-gc ones) build fine and pass tests (except the flaky one, bug #720). However, trying out one of these configurations (the default one) with threads caused a core dump in threads.tst. I've not checked out whether one of the many other memory model configurations would work fine with threads. [In case you wonder, I'll add libsigsegv to my build environment at a later time. After all, I've repeated often enough in this list that users should not use clisp without it :-)] Regards, Jörg ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel