I am trying to save a SBCL image with SWANK in it. For some reason it
seems to disappear. Here is what I do:
·······@klibb:~$ sbcl --no-userinit
This is SBCL 1.0.6, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/
>.
SBCL is free software, provided as is, with absolutely no
warranty.
It is mostly in the public domain; some portions are provided
under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
* (load "/usr/share/common-lisp/source/slime/swank-loader.lisp")
;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
fasl/sbcl-1.0.6-linux-x86/swank-backend.fasl"
;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
fasl/sbcl-1.0.6-linux-x86/nregex.fasl"
;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
fasl/sbcl-1.0.6-linux-x86/swank-source-path-parser.fasl"
;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
fasl/sbcl-1.0.6-linux-x86/swank-source-file-cache.fasl"
;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
fasl/sbcl-1.0.6-linux-x86/swank-sbcl.fasl"
;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
fasl/sbcl-1.0.6-linux-x86/swank-gray.fasl"
STYLE-WARNING:
implicitly creating new generic function STREAM-READ-CHAR-WILL-
HANG-P
;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
fasl/sbcl-1.0.6-linux-x86/swank.fasl"
WARNING: These Swank interfaces are unimplemented:
(CALLS-WHO DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-
RETURN
WHO-SPECIALIZES)
T
* (find-package :swank-loader)
#<PACKAGE "SWANK-LOADER">
Great! Now save the lisp image to file:
* (sb-ext:save-lisp-and-die "/home/mathias/test.core")
[undoing binding stack and other enclosing state... done]
[saving current Lisp image into /home/mathias/test.core:
writing 1912 bytes from the read-only space at 0x01000000
writing 2096 bytes from the static space at 0x01100000
writing 27680768 bytes from the dynamic space at 0x09000000
done]
Seems to go well, right?
Now starting with the new image:
·······@klibb:~$ sbcl --no-userinit --core test.core
This is SBCL 1.0.6, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/
>.
SBCL is free software, provided as is, with absolutely no
warranty.
It is mostly in the public domain; some portions are provided
under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
* (find-package :swank-loader)
NIL
*
Can anyone explain this?
/Mathias
On Mar 27, 6:37 pm, Mathias Dahl <············@gmail.com> wrote:
> I am trying to save a SBCL image with SWANK in it. For some reason it
> seems to disappear. Here is what I do:
>
> ·······@klibb:~$ sbcl --no-userinit
> This is SBCL 1.0.6, an implementation of ANSI Common Lisp.
> More information about SBCL is available at <http://www.sbcl.org/
>
> >.
>
> SBCL is free software, provided as is, with absolutely no
> warranty.
> It is mostly in the public domain; some portions are provided
> under
> BSD-style licenses. See the CREDITS and COPYING files in the
> distribution for more information.
> * (load "/usr/share/common-lisp/source/slime/swank-loader.lisp")
>
> ;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
> fasl/sbcl-1.0.6-linux-x86/swank-backend.fasl"
> ;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
> fasl/sbcl-1.0.6-linux-x86/nregex.fasl"
> ;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
> fasl/sbcl-1.0.6-linux-x86/swank-source-path-parser.fasl"
> ;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
> fasl/sbcl-1.0.6-linux-x86/swank-source-file-cache.fasl"
> ;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
> fasl/sbcl-1.0.6-linux-x86/swank-sbcl.fasl"
> ;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
> fasl/sbcl-1.0.6-linux-x86/swank-gray.fasl"
> STYLE-WARNING:
> implicitly creating new generic function STREAM-READ-CHAR-WILL-
> HANG-P
> ;; loading #P"/var/cache/common-lisp-controller/1000/sbcl/swank/
> fasl/sbcl-1.0.6-linux-x86/swank.fasl"
> WARNING: These Swank interfaces are unimplemented:
> (CALLS-WHO DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-
> RETURN
> WHO-SPECIALIZES)
> T
> * (find-package :swank-loader)
>
> #<PACKAGE "SWANK-LOADER">
>
> Great! Now save the lisp image to file:
>
> * (sb-ext:save-lisp-and-die "/home/mathias/test.core")
> [undoing binding stack and other enclosing state... done]
> [saving current Lisp image into /home/mathias/test.core:
> writing 1912 bytes from the read-only space at 0x01000000
> writing 2096 bytes from the static space at 0x01100000
> writing 27680768 bytes from the dynamic space at 0x09000000
> done]
>
> Seems to go well, right?
>
> Now starting with the new image:
>
> ·······@klibb:~$ sbcl --no-userinit --core test.core
> This is SBCL 1.0.6, an implementation of ANSI Common Lisp.
> More information about SBCL is available at <http://www.sbcl.org/
>
> >.
>
> SBCL is free software, provided as is, with absolutely no
> warranty.
> It is mostly in the public domain; some portions are provided
> under
> BSD-style licenses. See the CREDITS and COPYING files in the
> distribution for more information.
> * (find-package :swank-loader)
>
> NIL
> *
>
> Can anyone explain this?
>
> /Mathias
Use this instead:
$ sbcl --core test.core --no-userinit
--
Rommel M. Martinez
> Use this instead:
>
> $ sbcl --core test.core --no-userinit
How embarrassing... I was almost certain that some modules were saved
and some not but I tested now again and that simply isn't the case,
fortunately. I must have been confused when testing this and added the
--core argument at the end some of the times I tested. Strange that
SBCL doesn't say anything about the apparently unused --core argument
though...
Anyway, thanks a bunch!
/Mathias
On Mar 28, 12:18 am, Mathias Dahl <············@gmail.com> wrote:
> > Use this instead:
>
> > $ sbcl --core test.core --no-userinit
>
> How embarrassing... I was almost certain that some modules were saved
> and some not but I tested now again and that simply isn't the case,
> fortunately. I must have been confused when testing this and added the
> --core argument at the end some of the times I tested. Strange that
> SBCL doesn't say anything about the apparently unused --core argument
> though...
>
> Anyway, thanks a bunch!
>
> /Mathias
No problem. I had the same problem before, and one of my suspects
was the way SBCL handled command line arguments so I tried that.
(^o^)
--
Rommel M. Martinez