SBCL

threads and fork(), especially on darwin

Bug #310208 reported by Nikodemus Siivola
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Fix Released
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().

Nikodemus Siivola (nikodemus)
Changed in sbcl:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Nikodemus Siivola (nikodemus) wrote :

Some discussion of this on the mailing list:

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

Revision history for this message
Nikodemus Siivola (nikodemus) wrote :

And

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

Revision history for this message
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
Revision history for this message
Douglas Katzman (dougk) wrote :

this is obsolete. Marking it as fix released for lack of anything better.

Changed in sbcl:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.