[slime-devel] Re: Can not start slime-2.0 with clisp-2.33.2p1 on OpenBSD-4.1

[Zoong PHAM]

Hi Helmut,

On Thursday, 22 November 2007 at 22:24:10 +0100, Helmut Eller wrote:
> You could try this with Slime 2.0 and CLISP 2.33:

OK. I got back to Slime 2.0 and CLISP 2.33.
I updated my ~/.emacs file accordingly.

> 1. start CLISP in a terminal and load the Swank server with 
>    (load "swank-loader.lisp")
> 
> 2. enable debug output with
>    (setq swank:*log-events* t)
> 
> 3. start the server
>    (swank:create-server)

>From terminal 1:
Copyright (c) Sam Steingold, Bruno Haible 2001-2004


[1]> (load "swank-loader.lisp")
;; Loading file swank-loader.lisp ...
WARNING:
No architecture feature found in (POWERPC PPC X86 X86-64 AMD64 I686 I586 I486 PC386 IAPX386 SPARC64 SPARC HPPA64 HPPA).
;;  Loading file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank-backend.fas ...
;;  Loaded file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank-backend.fas
;;  Loading file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/nregex.fas ...
;;  Loaded file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/nregex.fas
;;  Loading file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/xref.fas ...
;;  Loaded file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/xref.fas
;;  Loading file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/metering.fas ...
;;  Loaded file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/metering.fas
;;  Loading file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank-clisp.fas ...
WARNING:
Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<GENERIC-FUNCTION CALL-WITHOUT-INTERRUPTS>
WARNING:
Replacing method #<STANDARD-METHOD NIL> in #<GENERIC-FUNCTION LISP-IMPLEMENTATION-TYPE-NAME>
WARNING:
Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<GENERIC-FUNCTION SET-DEFAULT-DIRECTORY>
WARNING:
Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<GENERIC-FUNCTION ARGLIST>
WARNING:
Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<GENERIC-FUNCTION FORMAT-SLDB-CONDITION>
WARNING:
Replacing method #<STANDARD-METHOD NIL> in #<GENERIC-FUNCTION UNPROFILE-ALL>
WARNING:
DEFUN/DEFMACRO: redefining function BREAK in /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank-clisp.fas, was defined in /usr/obj/i386/clisp-2.33.2p1/build-i386/condition.fas
;;  Loaded file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank-clisp.fas
;;  Loading file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank-gray.fas ...
;;  Loaded file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank-gray.fas
;;  Loading file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank.fas ...
;;  Loaded file /usr/local/home/zoong/.slime/fasl/2006-04-20/clisp-2.33.2-unix-unknown/swank.fas
0 errors, 0 warnings

WARNING:
These Swank interfaces are unimplemented:

(ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER ALL-THREADS CALLS-WHO DISASSEMBLE-FRAME FIND-THREAD INSPECT-FOR-EMACS INTERRUPT-THREAD RECEIVE REMOVE-FD-HANDLERS
 REMOVE-SIGIO-HANDLERS SEND SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN SPAWN THREAD-ID TOGGLE-TRACE WHO-MACROEXPANDS WHO-SPECIALIZES)
;; Loaded file swank-loader.lisp
T
[2]> (setq swank:*log-events* t)
T
[3]> (swank:create-server)
;; Swank started at port: 4005.

>From terminal 2:
$ netstat -an | grep 4005
tcp        0      0  *.4005                 *.*                    LISTEN
$

> 4. in Emacs type `M-x slime-connect' 

>From terminal 3:
started emacs
I entered that command, and accepted default host '127.0.0.1' and port '4005'
Then this message appeared on the emacs frame (terminal 3):
Lisp connection closed unexpectedly: exited abnormally with code 256

> Emacs should then try to connect and you should see at least some
> output in the terminal.  Perhaps we can learn from that where the
> segmentation fault occurs.

on terminal 1, this meesage appeared:
Segmentation fault (core dumped)
And clisp terminated with this error code:
$ echo $?
139
$

Regards,
Zoong