(defun save-lisp-and-die (core-file-name &key
(toplevel #'toplevel-init)
- (purify #!+gencgc nil
- #!-gencgc t)
+ (purify t)
(root-structures ())
(environment-name "auxiliary")
(executable nil))
somewhat longer than the normal GC which is otherwise done, but
it's only done once, and subsequent GC's will be done less often
and will take less time in the resulting core file. See the PURIFY
- function. For platforms that use the generational garbage collector
- (x86 and x86-64) purification generally results in a loss of
- performance.
+ function. This parameter has no effect on platforms using the
+ generational garbage collector.
:ROOT-STRUCTURES
This should be a list of the main entry points in any newly loaded
This is reinitialized to reflect the working directory where the
saved core is loaded.
-Foreign objects loaded with SB-ALIEN:LOAD-SHARED-OBJECT are
-automatically reloaded on startup, but references to foreign symbols
-do not survive intact on all platforms: in this case a WARNING is
-signalled when saving the core. If no warning is signalled, then the
-foreign symbol references will remain intact. Platforms where this is
-currently the case are x86/FreeBSD, x86/Linux, x86/NetBSD,
-sparc/Linux, sparc/SunOS, and ppc/Darwin.
+Foreign objects loaded with SB-ALIEN:LOAD-SHARED-OBJECT are automatically
+reloaded on startup, but references to foreign symbols do not survive intact
+on all platforms: in this case a WARNING is signalled when saving the core. If
+no warning is signalled, then the foreign symbol references will remain
+intact. Platforms where this is currently the case are x86/FreeBSD, x86/Linux,
+x86/NetBSD, sparc/Linux, sparc/SunOS, and ppc/Darwin.
+
+On threaded platforms only a single thread may remain running after
+SB-EXT:*SAVE-HOOKS* have run. Applications using multiple threads can
+be SAVE-LISP-AND-DIE friendly by registering a save-hook that quits
+any additional threads, and an init-hook that restarts them.
This implementation is not as polished and painless as you might like:
* It corrupts the current Lisp image enough that the current process
needs to be killed afterwards. This can be worked around by forking
another process that saves the core.
- * It will not work if multiple threads are in use.
* There is absolutely no binary compatibility of core images between
different runtime support programs. Even runtimes built from the same
sources at different times are treated as incompatible for this
This isn't because we like it this way, but just because there don't
seem to be good quick fixes for either limitation and no one has been
sufficiently motivated to do lengthy fixes."
+ #!+gencgc
+ (declare (ignore purify root-structures environment-name))
+ (tune-hashtable-sizes-of-all-packages)
(deinit)
;; FIXME: Would it be possible to unmix the PURIFY logic from this
;; function, and just do a GC :FULL T here? (Then if the user wanted
;; access to it even after the GC has moved it.
#!+gencgc
(setf sb!vm::*restart-lisp-function* #'restart-lisp)
- (cond (purify
+ (cond #!-gencgc
+ (purify
(purify :root-structures root-structures
:environment-name environment-name)
(save-core nil))
(save-core t)))))
(defun deinit ()
- (dolist (hook *save-hooks*)
- (with-simple-restart (continue "Skip this save hook.")
- (funcall hook)))
- #!-win32 (when (fboundp 'cancel-finalization)
- (cancel-finalization sb!sys:*tty*))
+ (call-hooks "save" *save-hooks*)
+ (when (rest (sb!thread:list-all-threads))
+ (error "Cannot save core with multiple threads running."))
+ (float-deinit)
(profile-deinit)
(debug-deinit)
- (foreign-deinit))
+ (foreign-deinit)
+ (stream-deinit)
+ (deinit-finalizers))