Resent-From: mtbp@rci.rutgers.edu From: mtbp@rci.rutgers.edu Subject: Slime blows up with SBCL 1.0.2/Mac OS X Date: February 1, 2007 7:13:59 PM EST Resent-To: slime-devel@common-lisp.net To: slime-devel@common-lisp.net

Hi, when I try to start the version of slime in CVS tarfile from the website using M-x slime (with SBCL 1.0.2 on OS X/x86 as my CL implementation), I get the following rather intimidating error message:

=== begin scary thing

(progn (load "/Library/Application Support/Emacs/slime/slime/swank- loader.lisp" :verbose t) (funcall (read-from-string "swank:start- server") "/tmp/slime.7829" :coding-system "iso-latin-1-unix"))

This is SBCL 1.0.2, an implementation of ANSI Common Lisp. More information about SBCL is available at http://www.sbcl.org/.

SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/Library/Application Support/Emacs/slime/slime/swank- loader.lisp" ; compiling file "/Library/Application Support/Emacs/slime/slime/ swank-backend.lisp" (written 19 DEC 2006 05:47:36 AM): Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded. 0: (BACKTRACE 536870911 #<SYNONYM-STREAM :SYMBOL SB-SYS:*TTY* {100C9831}>) 1: ((LAMBDA NIL)) 2: ((LAMBDA NIL)) 3: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA NIL) {11CD7D6D}>) 4: (SB-IMPL::ERROR-ERROR) 5: (SB-IMPL::INFINITE-ERROR-PROTECTOR) 6: (ERROR TYPE-ERROR) Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded. 0: (BACKTRACE 536870911 #<SYNONYM-STREAM :SYMBOL SB-SYS:*TTY* {11CE0E91}>) 1: ((LAMBDA NIL)) 2: ((LAMBDA NIL)) 3: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA NIL) {11CE0FAD}>) 4: (SB-IMPL::ERROR-ERROR) 5: (SB-IMPL::INFINITE-ERROR-PROTECTOR) ; ; compilation unit aborted ; caught 1 fatal ERROR condition ; compilation aborted after 0:00:01 6: *

=== end scary thing

I have no idea what's going on here. I do know that SLIME seems to be working fine with CLISP, though.

Many thanks, Matt