I found when this problem happens. During compile time I run a test suite which calls http-request with ssl connection. If I exclude my ssl related connections from compile time, this problem doesn't happen when I load my project image. 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? Thank you, Andrei On Tue, Mar 10, 2009 at 5:24 AM, Edi Weitz <e...@agharta.de> wrote: > On Tue, Mar 10, 2009 at 2:22 AM, Andrei Stebakov <lisper...@gmail.com> wrote: >> I wonder if it only happens on my system? > > Can anyone reproduce this? Or rather, does the SBCL/SSL combo work for > others? > > Thanks, > Edi. > > _______________________________________________ > drakma-devel mailing list > drakma-devel@common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-devel > _______________________________________________ drakma-devel mailing list drakma-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-devel
