With that change, I'm no longer getting the backtrace. However, Swank starts up at port 37470 and then the echo area shows "Connecting to Swank on port 37470..". It simply hangs here. This is the latest CVS SLIME and SBCL (as of ten minutes ago).
On 7/19/06, Christophe Rhodes csr21@cam.ac.uk wrote:
Juho Snellman jsnell@iki.fi writes:
atkinw@rpi.edu wrote:
Using the latest SBCL and the latest SLIME, I'm having trouble
load-op'ing
swank (or systems that depend on it). I either evaluate (asdf:oos 'asdf:load-op :swank) or do ,load-system swank RET. In either case,
ASDF
goes to work and some output is printed ot the REPL buffer. Then the
output
abruptly stops. the *inferior-lisp* buffer shows a backtrace
(attached).
This is an x86 Linux machine. I tried clearing ~/.slime/fasl as well.
http://common-lisp.net/pipermail/slime-devel/2006-May/004955.html
(I think Christophe has a patch to make Swank do the right thing here, which was something like replacing the default DEFMETHOD in DEFINTERFACE with a specialization on NO-APPLICABLE-METHOD. But it looks like it was never sent to the list.)
Actually, I did, but in June :-)
http://common-lisp.net/pipermail/slime-devel/2006-June/005028.html
Cheers,
Christophe
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ Sbcl-devel mailing list Sbcl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sbcl-devel