Re: reader & threads problem

[Vladimir T. <vtz...@gm...>]

On 12/30/09, Sam Steingold <sd...@gn...> wrote:
> "make check-tests-parallel" succeeded for me for the first time!
I have much better success rate :).
I test with disabled clos & mop tests (however clos is involved in
many other tests) - deadlocks&segfault may happen when
accessing&modifying hashtables behind clos/mop (ones defined in
clos-class5.lisp).
Looks like hashtables (in general) can cause segfaults/deadlock when
used without synchronization - this is one of the things I am looking
in now.
Also the "The Exception to the Immutability Rule" mentioned in
http://clisp.cons.org/impnotes/comp-fun.html probably causes problems.

> however, the terminal is still left in the raw state, a reset was required.
I've never experienced this problem. Any ideas what may cause this?