Clever Geek Handbook

Slimv segfault on OS X Lion

I've been trying to get slimv (http://www.vim.org/scripts/ script.php? Script_id = 2531) working for a while, but I'm really not sure what else I can do.

I am running vim 7.3 compiled with python support using clisp (sbcl shows the same issue) on os x lion. I pulled the latest slimv from vim.org.

When I load the lisp file, echo g: slimv_loaded returns 1, but I don't get the second window with repl. When I hit any of the keys, a new terminal window opens, clisp starts and returns the following

; Loading file /Users/pdk/.vim/slime/start-swank.lisp ...
;;  Loading file /Users/pdk/.vim/slime/swank-loader.lisp ...
WARNING: No architecture feature found in
     (POWERPC PPC X86 X86-64 X86_64 AMD64 I686 I586 I486 PC386 IAPX386
     SPARC64 SPARC
     HPPA64 HPPA ARM PENTIUM3 PENTIUM4 JAVA-1.4 JAVA-1.5 JAVA-1.6
     JAVA-1.7).
;;  Loaded file /Users/pdk/.vim/slime/swank-loader.lisp
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-backend.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-backend.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/xref.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/xref.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/metering.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/metering.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-clisp.fas ...
WARNING: DEFUN/DEFMACRO: redefining function BREAK in
         /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-clisp.fas,
         was defined in
         /private/tmp/homebrew-clisp-2.49-LWCF/clisp-2.49/src/condition.fas
WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in
         #<STANDARD-GENERIC-FUNCTION EMACS-INSPECT>
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-clisp.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-gray.fas ...
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-WRITE-CHAR>
         is being modified, but has already been called.
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-COLUMN>
         is being modified, but has already been called.
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-FORCE-OUTPUT>
         is being modified, but has already been called.
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-COLUMN>
         is being modified, but has already been called.
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-gray.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-match.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-match.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-rpc.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank-rpc.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/swank.fas
WARNING: These Swank interfaces are unimplemented:
         (ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER
         BACKGROUND-SAVE-IMAGE
         DISASSEMBLE-FRAME DUP EXEC-IMAGE FRAME-CALL INTERRUPT-THREAD
         MAKE-FD-STREAM
         RECEIVE-IF REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SEND
         SLDB-BREAK-AT-START
         SLDB-BREAK-ON-RETURN SLDB-STEP-INTO SLDB-STEP-NEXT SLDB-STEP-OUT
         SOCKET-FD
         SPAWN TOGGLE-TRACE)
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-c-p-c.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-c-p-c.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-arglists.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-arglists.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-fuzzy.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-fuzzy.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-fancy-inspector.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-fancy-inspector.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-presentations.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-presentations.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-presentation-streams.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-presentation-streams.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-package-fu.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-package-fu.fas
;;  Loading file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-hyperdoc.fas ...
;;  Loaded file /Users/pdk/.slime/fasl/2011-03-13/clisp-2.49-unix-unknown/contrib/swank-hyperdoc.fas
;; Swank started at port: 4005.
CL-USER> 
;; swank:close-connection: 
READ: input stream #<IO UNBUFFERED SOCKET-STREAM CHARACTER 0.0.0.0:4005> has reached its end

;; swank:close-connection: NIL

at the same time, the original terminal window closes vim and shows this

tab 1 of window id 57924
Vim: Caught deadly signal SEGV

Vim: Finished.
[1]    83648 segmentation fault  vim foo.lisp

Any ideas what I can do?

+1


source to share


2 answers


I just got the following information from a macvim developer:



It seems to be a 64-bit issue - compiling MacVim 32-bit fixes it. Compile the 32 bit version. The build instructions here to build a 32-bit "configure" string must include the "--with-macarchs = i386" flag.

+1


source


  • If you change log = True

    on line 32 of swank.py

    then Slimv writes a named log file swank.log

    containing the communication data between the swank client and the server. This can be used to check for any problems with the swank protocol. You can send the log file to the Slimv author (what me :) for analysis.
  • You can try to run your own swank server from Slime manually, then let Slimv connect it. This can help if the Swank server bundled with Slimv is not fully Lion compatible.
  • You can try the most recent version taken from the Slimv repository .


0


source






More articles:


All Articles