threads and fork(), especially on darwin

Bug #310208 reported by Nikodemus Siivola on 2008-12-21
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Low
Unassigned

Bug Description

Threaded darwin builds fail a host of impure tests -- but only if the threads.pure.lisp
has been run before.

This seems to be due to the thread-stack freeing logic running afoul of fork().

Changed in sbcl:
importance: Undecided → Medium
status: New → Confirmed
Nikodemus Siivola (nikodemus) wrote :

Some discussion of this on the mailing list:

  http://article.gmane.org/gmane.lisp.steel-bank.devel/12810

Nikodemus Siivola (nikodemus) wrote :

Importance downgraded to low as SBCL 1.0.37.47 made the thread tests reasonably runnable on Darwin. (Many fail horribly, but at least they can be run.)

Changed in sbcl:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers