Reputation: 588
So, I am using
sbcl --dynamic-space-size 1024 \
--noinform \
--load $HOME/quicklisp/setup.lisp \
--eval '(ql:quickload :myapp)' \
--eval "(sb-ext:save-lisp-and-die \"myapp\" :toplevel #'myapp::main :executable t :compression t)"
to generate myapp
locally, and uploading the resulting binary to the server.
The function myapp:main
executes the following (along with several other initialization things for the server) as pointed here:
(bt:make-thread (lambda () (swank:create-server :port swank-port ; consider it to be 8080
:dont-close t)))
I also do the port forwarding on my local machine:
ssh -L8080:127.0.0.1:8080 user@remote
I can slime-connect
to it, when myapp
is run on my local machine, with me connecting to it from the same machine.
However, when I try to slime-connect
to localhost
, 8080
on my local machine, with myapp
running on remote, I get the error as
Can't locate module: SWANK-IO-PACKAGE::SWANK-TRACE-DIALOG
[Condition of type SIMPLE-ERROR]
Restarts:
0: [*ABORT] Return to SLIME's top level.
1: [ABORT] abort thread (#<THREAD "worker" RUNNING {1005B6EB73}>)
If I choose [*ABORT]
, emacs gives me error in process filter: No catch for tag: slime-result-2-212, (error "Synchronous Lisp Evaluation aborted")
(in the minibuffer), with no SLIME REPL.
Choosing [ABORT]
also gives the almost same error in process filter: Synchronous Lisp Evaluation aborted
.
Also, if I try to evaluate something in the frame, too, I get the error in process filter: Invalid message protocol
.
PS: I am using AWS, in case the details about Security Groups are relevant.
Upvotes: 3
Views: 399