13.03.09, 20:49, "Edi Weitz" <e...@agharta.de>:
> On Fri, Mar 13, 2009 at 5:09 PM, Andrei Stebakov <lisper...@gmail.com> wrote: > > Basically, to reproduce it for me it's enough to put in the following > > code in the top level: > > > > (eval-when (:compile-toplevel :load-toplevel :execute) > > (http-request "https://www.fortify.net/cgi/ssl_2.pl";) ) > > > > Then I compile the project with (sb-ext:save-lisp-and-die "myproj" > > :toplevel #'my-toplevel :executable t :purify t). > > When I load the image and any attempt to call http-request with ssl > > causes that memory corruption. > > Does it mean cl+ssl library shouldn't be called at compile time? > I think it means that something in cl+ssl or the libraries it uses > doesn't clean up properly after itself in SBCL and doesn't survive > saving of the image. Most likely some FFI thingy. (I.e. this is not > a compile time issue but is related to saving images.) > Edi. Maybe it's necessary to call CL+SSL:RELOAD? From the cl+ssl docs: Function CL+SSL:RELOAD () Reload libssl. Call this function after restarting a Lisp core with CL+SSL dumped into it on Lisp implementations that do not reload shared libraries automatically. Best regards, - Anton _______________________________________________ drakma-devel mailing list drakma-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-devel
