X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Frun-program.lisp;h=1dad7f90faf569f0551fbef5ff4cee95ce70176a;hb=ea36d3d79b9dfe3598faca5e267efd5980b94d4a;hp=c4cc515b4edce323b4e7ccc697648175f8bba772;hpb=5108495b13b99452d5a85c4600f68432ff8894b2;p=sbcl.git

diff --git a/src/code/run-program.lisp b/src/code/run-program.lisp
index c4cc515..1dad7f9 100644
--- a/src/code/run-program.lisp
+++ b/src/code/run-program.lisp
@@ -10,7 +10,7 @@
 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
 ;;;; files for more information.
 
-(in-package "SB-IMPL")
+(in-package "SB-IMPL") ;(SB-IMPL, not SB!IMPL, since we're built in warm load.)
 
 ;;;; hacking the Unix environment
 ;;;;
@@ -46,6 +46,21 @@
 ;;;; visible at GENESIS time.
 
 (def-alien-variable "environ" (* c-string))
+(push (lambda ()
+	;; We redo this here to protect ourselves from this scenario:
+	;;   * Build under one version of shared lib, save a core.
+	;;   * Load core under another version of shared lib. ("Now
+	;;     where was environ again?" SIGSEGV, etc.)
+	;; Obviously it's a KLUDGE to do this hack for every alien
+	;; variable, but as it happens, as of sbcl-0.7.0 this is the
+	;; only alien variable used to implement SBCL, so it's not
+	;; worth coming up with a general solution. (A general
+	;; solution would be nice for users who want to have their
+	;; alien code be preserved across a save/load cycle, but this
+	;; problem with alien variables is only one of several
+	;; problems which'd need to be solved before that can happen.)
+        (def-alien-variable "environ" (* c-string)))
+      *after-save-initializations*)
 
 (defun posix-environ ()
   "Return the Unix environment (\"man environ\") as a list of SIMPLE-STRINGs."