HÃkon Alstadheim <hakon <at> alstadheim.priv.no> writes:
> Just on principle you should check whatever global state gets set on > initialization, both by cmucl (dynamic variables in MP) and by slime > (flags telling slime that connections are open etc.) These things need > to be set to nil or deleted before you save core. Look at the stuff that > saves cores during compilation in the CMUCL source for hints. One easy > way to get partway there would be to delete the SWANK package from your > image before you call save-lisp. You are going to exit anyway, so you > don't need the communication. A more tidy way that might still work > would be to call SLIME-DISCONNECT or whatever the function is called in [gmane asked me to remove quoted text] Thank you for your answer. Just deleting the swank package did not work. Unfortunately I think disconnecting SLIME is not enough. The problem is not SLIME but the fact that multiprocessing is being used. Thibault
