- slime-devel - mailman3.common-lisp.net

[slime-devel] Hints needed on why "Process inferior-lisp hangup" occurs
by Willem Rein Oudshoorn 02 Jun '09

02 Jun '09

I need some hints to start figuring out why I regularly get a "Process inferior-lisp hangup" in my *inferior-lisp* buffer, but I do not have clue where to start. Situation: * OS: Mac OS X * Lisp version: sbcl 64bit 1.0.28 and ccl 1.3-r12156M (64bit) * Slime version: CVS version as of today. "Reproduction Scenario" 1 Start slime with one of the two lisp implementaitons mentioned above 2 Open "/dev/tty.NXT-DevB-1", which is a serial blue tooth connection to a Lego NXT brick. 3 Turn of the Lego NXT brick (the other side of the serial connection) After this, I get the "Process inferior-lisp hangup" in the *inferior-lisp* buffer. In contrast, if I do not run this through slime, but just run it from a terminal the lisp implementaiton is not killed. I assume that the serial bluetooth connection is closed from the other side and that that somehow closes also the slime connection. But I don't know why, if this is normal, and how to change this behaviour. All hints are appreciated. Wim Oudshoorn.

3 5

[slime-devel] Connection to Emacs lost. condition: junk in string
by Andrei Stebakov 02 Jun '09

02 Jun '09

Recently when I evaluate a relatively big function in slime (more that 6 lines of code) I lose connection with swank. I tried Emacs with different versions and slime with different versions, so I don't know where else I can look for an error. Could it be something with network on this particular workstation? The stack is following (for the particular function what failed to evaluate): close-connection: junk in string " (setf" ... deinstall-fd-handler ;; Event history end. ;; Backtrace: (0 ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN)) #<FUNCTION (LAMBDA #) {A11068D}>)) (1 (SWANK::SAFE-BACKTRACE)) (2 (SWANK::MAKE-SWANK-ERROR #<SWANK::SWANK-ERROR {C9492F9}>)) (3 ((FLET #:LAMBDA2855) #<SWANK::SWANK-ERROR {C9492F9}>)) (4 (SIGNAL #<SWANK::SWANK-ERROR {C9492F9}>)[:EXTERNAL]) (5 (ERROR #<SWANK::SWANK-ERROR {C9492F9}>)[:EXTERNAL]) (6 ((FLET #:LAMBDA2855) #<SB-INT:SIMPLE-PARSE-ERROR {C750239}>)) (7 (SIGNAL #<SB-INT:SIMPLE-PARSE-ERROR {C750239}>)[:EXTERNAL]) (8 (ERROR SB-INT:SIMPLE-PARSE-ERROR)[:EXTERNAL]) (9 (PARSE-INTEGER " (setf")[:EXTERNAL]) (10 (SWANK::READ-PACKET #<SB-SYS:FD-STREAM for "a socket" {C5C30E1}>)) (11 (SWANK::DECODE-MESSAGE #<SB-SYS:FD-STREAM for "a socket" {C5C30E1}>)) (12 (SWANK::WAIT-FOR-EVENT/EVENT-LOOP (OR (:EMACS-REX . SWANK::_) (:EMACS-CHANNEL-SEND . SWANK::_)) T)) (13 (SWANK::WAIT-FOR-EVENT (OR (:EMACS-REX . SWANK::_) (:EMACS-CHANNEL-SEND . SWANK::_)) T)) (14 (SWANK::PROCESS-REQUESTS T)) (15 (SB-IMPL::SUB-SUB-SERVE-EVENT NIL NIL)) (16 (SB-IMPL::SUB-SERVE-EVENT NIL NIL NIL)) (17 (SB-SYS:WAIT-UNTIL-FD-USABLE 10 :INPUT NIL)) (18 (SB-IMPL::REFILL-INPUT-BUFFER #<SB-SYS:FD-STREAM for "a socket" {C5C30E1}>)) (19 (SB-IMPL::INPUT-CHAR/UTF-8 #<SB-SYS:FD-STREAM for "a socket" {C5C30E1}> NIL :EOF)) (20 (SB-IMPL::ANSI-STREAM-READ-CHAR #<SB-SYS:FD-STREAM for "a socket" {C5C30E1}> NIL :EOF #<unavailable argument>)) (21 (SB-IMPL::ANSI-STREAM-READ-SEQUENCE ..)) (22 (READ-SEQUENCE ..)[:EXTERNAL]) (23 (SWANK::READ-CHUNK #<SB-SYS:FD-STREAM for "a socket" {C5C30E1}> 627)) (24 (SWANK::READ-PACKET #<SB-SYS:FD-STREAM for "a socket" {C5C30E1}>)) (25 (SWANK::DECODE-MESSAGE #<SB-SYS:FD-STREAM for "a socket" {C5C30E1}>)) (26 (SWANK::WAIT-FOR-EVENT/EVENT-LOOP (OR (:EMACS-REX . SWANK::_) (:EMACS-CHANNEL-SEND . SWANK::_)) T)) (27 (SWANK::WAIT-FOR-EVENT (OR (:EMACS-REX . SWANK::_) (:EMACS-CHANNEL-SEND . SWANK::_)) T)) (28 (SWANK::PROCESS-REQUESTS T)) (29 ((LAMBDA ()))) (30 ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {C74E74D}>)) (31 (SWANK::CALL-WITH-BINDINGS ..)) (32 (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {C5C3A79}> #<CLOSURE (LAMBDA #) {C74E74D}>)) (33 (SWANK::HANDLE-REQUESTS #<SWANK::CONNECTION {C5C3A79}> T)) (34 (SB-IMPL::SUB-SUB-SERVE-EVENT NIL NIL)) (35 (SB-IMPL::SUB-SERVE-EVENT NIL NIL NIL)) (36 (SB-SYS:WAIT-UNTIL-FD-USABLE 0 :INPUT NIL)) (37 (SB-IMPL::REFILL-INPUT-BUFFER #<SB-SYS:FD-STREAM for "standard input" {C10A859}>)) (38 (SB-IMPL::INPUT-CHAR/UTF-8 #<SB-SYS:FD-STREAM for "standard input" {C10A859}> NIL #:EOF-OBJECT)) (39 (READ-CHAR #<SB-SYS:FD-STREAM for "standard input" {C10A859}> NIL #:EOF-OBJECT #<unused argument>)) (40 (READ-CHAR #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {9137511}> NIL #:EOF-OBJECT #<unused argument>)) (41 (SB-IMPL::%READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {9137511}> NIL (NIL) T)) (42 (SB-IMPL::%READ-PRESERVING-WHITESPACE #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {9137511}> NIL (NIL) NIL)) (43 (READ #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {9137511}> NIL (NIL) NIL)) (44 (SB-IMPL::REPL-READ-FORM-FUN #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDIN* {9137511}> #<unavailable argument>)) (45 (SB-IMPL::REPL-FUN NIL)) (46 ((LAMBDA ()))) (47 (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA #) {C5AAAFD}>)) (48 (SB-IMPL::TOPLEVEL-REPL NIL)) (49 ((LABELS SB-IMPL::RESTART-LISP))) ;; Connection to Emacs lost. [ ;; condition: junk in string " (setf" ;; type: SWANK::SWANK-ERROR ;; encoding: NIL style: :FD-HANDLER dedicated: NIL] Thank you, Andrei

2 1

[slime-devel] [PATCH] Output redirection in the SIMPLE-SERVE-EVENTS case.
by Samium Gromoff 01 Jun '09

01 Jun '09

Good day folks, The following patch fixes the *standard-output* not being redirected into the *slime-repl* buffer on SBCL/win32 specifically, and in all cases when connection communication style is NIL, in general. The problem appeared in the CVS commit dated 2008-12-24 11:14:06, which moved environment capture past the point where the event handlers were entering the binding of the stream variables, which is set from the environment. The fix was tested on Linux/x86/SBCL-1.0.22 and MinGW/SBCL-1.0.28.43. commit 87cd4f6167e0b9695a279d8c64e1f4876a001e0a Author: Samium Gromoff <_deepfire(a)feelingofgreen.ru> Date: Wed May 13 23:44:52 2009 +0400 Capture stream globals before the request servers are called. diff --git a/swank.lisp b/swank.lisp index a0646c2..90418f2 100644 --- a/swank.lisp +++ b/swank.lisp @@ -1408,6 +1408,16 @@ The processing is done in the extent of the toplevel restart." :serve-requests #'simple-serve-requests)) ))) (setf (connection.communication-style c) style) + (initialize-streams-for-connection c) + (with-struct* (connection. @ c) + (setf (@ env) + `((*standard-output* . ,(@ user-output)) + (*standard-input* . ,(@ user-input)) + (*trace-output* . ,(or (@ trace-output) (@ user-output))) + (*error-output* . ,(@ user-output)) + (*debug-io* . ,(@ user-io)) + (*query-io* . ,(@ user-io)) + (*terminal-io* . ,(@ user-io))))) (setf success t) c) (unless success @@ -1569,16 +1579,7 @@ NIL if streams are not globally redirected.") (defslimefun create-repl (target) (assert (eq target nil)) (let ((conn *emacs-connection*)) - (initialize-streams-for-connection conn) (with-struct* (connection. @ conn) - (setf (@ env) - `((*standard-output* . ,(@ user-output)) - (*standard-input* . ,(@ user-input)) - (*trace-output* . ,(or (@ trace-output) (@ user-output))) - (*error-output* . ,(@ user-output)) - (*debug-io* . ,(@ user-io)) - (*query-io* . ,(@ user-io)) - (*terminal-io* . ,(@ user-io)))) (maybe-redirect-global-io conn) (when (use-threads-p) (setf (@ repl-thread) (spawn-repl-thread conn "repl-thread"))) regards, Samium Gromoff

2 1

[slime-devel] Lispbox SLIME 2.0 version output goes to *inferior-lisp* buffer instead of to *slime-repl clisp-2.37* buffer on Windows XP Professional, Service Pack 3
by Benjamin L. Russell 01 Jun '09

01 Jun '09

The output of the following program solving the Towers of Hanoi problem in Common Lisp directs the output of the "format" statement to the "*inferior-lisp*" buffer instead of to the "*slime-repl clisp-2.37*" buffer on Windows XP Professional, Service Pack 3: >(defun hanoi (n) > (hanoi-helper n 'A 'B 'C)) > >(defun hanoi-helper (n source dest using) > (cond ((equalp n 1) (format t "Move disc from ~A to ~A.~%" source dest)) > (t (progn > (hanoi-helper (- n 1) source using dest) > (hanoi-helper 1 source dest using) > (hanoi-helper (- n 1) using dest source))))) When "M-x slime-redirect-inferior-output RET" is invoked in Lispbox Emacs, the output is redirected correctly, but so is the rest of the output to the "*inferior-lisp*" buffer. This is not a clean solution. Does anybody know how to get the above hanoi-helper procedure to direct the output of the "format" statement correctly to the REPL, instead of to the "*inferior-lisp*" buffer? (This point is probably not relevant, but I have reconfigured Lispbox to call my .emacs file using my existing GNU Emacs 22.3.1 installation.) -- Benjamin L. Russell -- Benjamin L. Russell / DekuDekuplex at Yahoo dot com http://dekudekuplex.wordpress.com/ Translator/Interpreter / Mobile: +011 81 80-3603-6725 "Furuike ya, kawazu tobikomu mizu no oto." -- Matsuo Basho^

1 4

[slime-devel] Daily ChangeLog diff
by Helmut Eller 29 May '09

29 May '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1772 slime/ChangeLog:1.1776 --- slime/ChangeLog:1.1772 Sun May 24 08:58:50 2009 +++ slime/ChangeLog Thu May 28 15:01:09 2009 @@ -1,3 +1,36 @@ +2009-05-28 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (def-slime-test): Forgot to remove debugging code. + +2009-05-28 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-dispatch-event :emacs-rex): Make sure that we + pop the continuation on erroneous send. + + Patch by Mark Cox <markcox80(a)gmail.com>. + +2009-05-28 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp (tokenize-symbol-thoroughly): Make it work correctly + on escaped symbols. + +2009-05-28 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-disconnect): Now only disconnects one + connection, current one by default, or given by argument. + (slime-disconnect-all): New. What `slime-disconnect' was before. + (def-slime-test): Changed: expected failures are now given + by (:fails-for ...) clauses. Extended: new clause (:style ...) to + have a test run only on a certain communication style. Updated + existing test cases accordingly. + ([struct] slime-test): New slot `skipped'. + (slime-skipped-tests): New var. + (slime-execute-tests): Adapted accordingly. + ([test] disconnect): Renamed to `disconnect-and-reconnect' + ([test] disconnect-one-conneciton): New. + + Adapted from patch by Stas Boukarev. + 2009-05-24 Tobias C. Rittweiler <tcr(a)freebits.de> * slime.el ([test] fancy-symbol-names): Add cases involving #| Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.214 slime/contrib/ChangeLog:1.215 --- slime/contrib/ChangeLog:1.214 Wed May 20 15:25:58 2009 +++ slime/contrib/ChangeLog Thu May 28 11:40:10 2009 @@ -1,3 +1,10 @@ +2009-05-28 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime-repl.el (slime-repl-disconnect): Disconnect current connection. + (slime-repl-disconnect-all): New; disconnect all connections. + + Patch by Stas Boukarev. + 2009-05-20 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-arglists.lisp (arglist-dispatch [define-compiler-macro]):

1 0

[slime-devel] Indentation of WITH-SLOTS and WITH-ACCESSORS
by Daniel White 28 May '09

28 May '09

The current behaviour of slime-indentation is to indent them like MULTIPLE-VALUE-BIND. (with-slots (x y z) object (list x y z)) (with-accessors (x y z) object (list x y z)) However, the Hyperspec and a number of other books seem to suggest that the instance argument lines up with the parameters. (with-slots (x y z) object (list x y z)) (with-accessors (x y z) object (list x y z)) I've attached a patch that will format these forms like the second example. -- Daniel White

2 2

[slime-devel] [Patch]: slime-repl-disonnect disconnecting all connection
by Stas Boukarev 28 May '09

28 May '09

contrib/slime-repl.el: (slime-repl-disonnect) rename to slime-repl-disonnect-all. (slime-repl-disonnect): disconnect only the currnet connection. -- With best regards, Stas.

2 4

[slime-devel] slime-autodoc stopping because of invalid characters.
by Mark Cox 28 May '09

28 May '09

Hi all, Occasionally I manage to input a strange character into the slime-repl and try and send it to the lisp. Fortunately, there is a condition in SLIME-NET-SEND in slime.el which detects for strange characters and refuses to send them. However, after signalling the "Coding system ..." error in that function, the slime-autodoc/eldoc support for the REPL stops working. The attached patch fixes that issue. Is it correct to send CONTINUATION the value (LIST :ABORT)? I have seen uses of SLIME-REX which look for it. Thanks Mark P.S. I'm a newbie to emacs lisp and the inner workings of slime.

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 25 May '09

25 May '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1770 slime/ChangeLog:1.1772 --- slime/ChangeLog:1.1770 Sat May 23 12:48:16 2009 +++ slime/ChangeLog Sun May 24 08:58:50 2009 @@ -1,3 +1,17 @@ +2009-05-24 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el ([test] fancy-symbol-names): Add cases involving #| + ... |# style comments. Currently failing. + + Reported by Madhu. + +2009-05-24 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-goto-location-position): Only go to match-beginning if + search succeeded. + + Patch by Madhu. + 2009-05-23 Helmut Eller <heller(a)common-lisp.net> * swank-openmcl.lisp (break-in-sldb): Honor *break-on-signals*.

1 0

[slime-devel] parser state bugs
by Madhu 24 May '09

24 May '09

Consider the following content in a slime buffer with the cursor at the point indicated by the caret |# (defun foo () (getf ^ (slime-symbol-at-point) returns nil. It should return "getf". [I thought I had isolated myself from this department by setting `slime-highlight-suppressed-forms' to nil. Could all buffer fontification code please be moved to an optional contrib? including the complexities involved in department] -- Madhu

2 5