From: Nikodemus S. <nik...@ra...> - 2008-10-07 20:28:07
|
On Tue, Oct 7, 2008 at 10:30 PM, Harald Hanche-Olsen <ha...@ma...> wrote: > + "Nikodemus Siivola" <nik...@ra...>: > >> I'm 80% sure this is the same fork() and thread-stack problem that >> plagues Darwin. What happens if you do >> >> sh run-tests.sh *.impure.lisp >> >> ? > > Hmm, funny. This happened, all with no action on my part: > > [... 2.5 megabytes of output ...] > Finished running tests. > Status: > Expected failure: callback.impure.lisp / UNDERFLOW-DETECTION > Unexpected success: debug.impure.lisp / (UNDEFINED-FUNCTION BUG-346) > Expected failure: debug.impure.lisp / (UNDEFINED-FUNCTION BUG-353) > Expected failure: external-format.impure.lisp / (CHARACTER-DECODE-LARGE > FORCE-END-OF-FILE) > Expected failure: packages.impure.lisp / USE-PACKAGE-CONFLICT-SET > Expected failure: packages.impure.lisp / IMPORT-SINGLE-CONFLICT > ok > //apparent success (reached end of run-tests.sh normally) > > "Unexpected success", that was ... unexpected. That is just a symptom of the slightly brittle backtracing. Did you run all tests, or just the impure ones? If the latter, then you original set of failures is almost certainly a symptom of bad interaction between threads and fork() -- as long as you don't fork() in threaded programs, using the threaded build should be fine. Cheers, -- Nikodemus |