The CMUCL manual says that "if a Lisp core image is saved (using
SAVE-LISP), all loaded foreign code is lost when the image is
restarted."

OK. I have a Lisp image which uses a foreign library (namely my CL-GD
stuff) and if I SAVE-LISP this image and then try to invoke it with
"lisp -core ..." I get a message like 

  Error in batch processing:
  Undefined foreign symbol: "gdImageCreateTrueColor"

as expected.

Now, when I change the init-function of this core file to first reload
the foreign library with ALIEN:LOAD-FOREIGN I get another error,
namely

  Error in batch processing:
  Error in function UNIX::SIGSEGV-HANDLER:  Segmentation Violation at #x40007409.

which doesn't happen if I don't work from a saved core.

What is the correct way to deal with saved cores and foreign libraries
in CMUCL? Or can't this be done?

(18e on Linux x86f.)

Thanks,
Edi.



Reply via email to