From mhd at yv.org Fri Jul 19 05:46:29 2019 From: mhd at yv.org (Mark H. David) Date: Thu, 18 Jul 2019 22:46:29 -0700 Subject: slime meta-dot in ASDF sources [cross-post from ASDF-devel] Message-ID: <019ba3a1-d3c8-46f2-8299-5015f025d558@www.fastmail.com> [The main ASDF dev Robert Goldman answered this partly in ASDF-devel mailing list, but in doing so led me to believe the SLIME devs would know more, hence the crosspost. -MHD] How do ASDF developers using emacs with SLIME deal with doing meta-dot (meta-.) on function names in ASDF sources. Out of the box, mostly when I meta-. just goes to one big top-level form that starts like this (with-upgradability () (define-condition invalid-source-registry (invalid-configuration warning) Thanks for clues, -Mark From stassats at gmail.com Fri Jul 19 11:08:29 2019 From: stassats at gmail.com (Stas Boukarev) Date: Fri, 19 Jul 2019 14:08:29 +0300 Subject: slime meta-dot in ASDF sources [cross-post from ASDF-devel] In-Reply-To: <019ba3a1-d3c8-46f2-8299-5015f025d558@www.fastmail.com> References: <019ba3a1-d3c8-46f2-8299-5015f025d558@www.fastmail.com> Message-ID: The macros like with-upgradability transform the code erasing any links to the original source, making it impossible to locate. On Fri, Jul 19, 2019 at 8:47 AM Mark H. David wrote: > > [The main ASDF dev Robert Goldman answered this partly in ASDF-devel mailing list, but in doing so led me to believe the SLIME devs would know more, hence the crosspost. -MHD] > > > How do ASDF developers using emacs with SLIME deal with doing meta-dot (meta-.) on function names in ASDF sources. Out of the box, mostly when I meta-. just goes to one big top-level form that starts like this > > (with-upgradability () > (define-condition invalid-source-registry (invalid-configuration warning) > Thanks for clues, > -Mark > From achirvasub at gmail.com Tue Jul 23 13:29:10 2019 From: achirvasub at gmail.com (Stuart Little) Date: Tue, 23 Jul 2019 09:29:10 -0400 Subject: slime + clisp + emacs: server disconnects Message-ID: <20190723132910.GB9426@chirva-void> I am running - emacs 26.2 - slime 2.24 - clisp 2.49 on Linux. Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: Lisp connection closed unexpectedly: connection broken by remote peer The inferior-lisp buffer reads as follows after the disconnect: --- buffer starts --- (progn (load "/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I \ `+' / I 8 8 8 8 8 8 \ `-+-' / 8 8 8 ooooo 8oooo `-__|__-' 8 8 8 8 8 | 8 o 8 8 o 8 8 ------+------ ooooo 8oooooo ooo8ooo ooooo 8 Welcome to GNU CLISP 2.49 (2010-07-07) Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2010 Type :h and hit Enter for context help. [1]> ;; Loading file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ... ;; Loaded file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ... WARNING: DEFUN/DEFMACRO: redefining function BREAK in /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, was defined in /builddir/clisp-2.49/src/condition.fas WARNING: Replacing method #)> in # ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... WARNING: The generic function # is being modified, but has already been called. WARNING: The generic function # is being modified, but has already been called. WARNING: The generic function # is being modified, but has already been called. ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas 0 errors, 5 warnings ;; Swank started at port: 41975. CL-USER> ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ... ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ... WARNING: The generic function # is being modified, but has already been called. WARNING: Replacing method # (EQL :FIND-EXISTING))> in # ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ... ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas ... WARNING: Test failed: (&KEY #'#'+) => "(&key (function #'+))" Expected: One of: "(&key (function #'+))", "(&key (function (function +)))" ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas Process inferior-lisp segmentation fault --- buffer ends --- More information: - starting clisp in a terminal all on its own seems to work fine; I haven't had segmentation faults using it in isolation from slime. - I tried to start the server from within clisp and connect to it: (a) rlwrap clisp (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") (c) (swank-loader::init :reload t) (d) (swank:create-server :port 7000) (e) from within emacs: M-x slime-connect with localhost and port 7000 Same behavior as before: I get connected, get to make a few evaluations, get disconnected. This time around rlwrap tells me (in the terminal where I started clisp): rlwrap: warning: clisp crashed, killed by SIGSEGV From stassats at gmail.com Tue Jul 23 13:52:00 2019 From: stassats at gmail.com (Stas Boukarev) Date: Tue, 23 Jul 2019 16:52:00 +0300 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <20190723132910.GB9426@chirva-void> References: <20190723132910.GB9426@chirva-void> Message-ID: It says that Clisp crashes with a segfault, nothing to do with slime. On Tue, Jul 23, 2019 at 4:30 PM Stuart Little wrote: > > I am running > > - emacs 26.2 > - slime 2.24 > - clisp 2.49 > > on Linux. > > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > Lisp connection closed unexpectedly: connection broken by remote peer > > The inferior-lisp buffer reads as follows after the disconnect: > > --- buffer starts --- > > (progn (load "/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) > > i i i i i i i ooooo o ooooooo ooooo ooooo > I I I I I I I 8 8 8 8 8 o 8 8 > I \ `+' / I 8 8 8 8 8 8 > \ `-+-' / 8 8 8 ooooo 8oooo > `-__|__-' 8 8 8 8 8 > | 8 o 8 8 o 8 8 > ------+------ ooooo 8oooooo ooo8ooo ooooo 8 > > Welcome to GNU CLISP 2.49 (2010-07-07) > > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 > Copyright (c) Sam Steingold, Bruno Haible 2001-2010 > > Type :h and hit Enter for context help. > > [1]> > ;; Loading file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ... > ;; Loaded file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ... > WARNING: DEFUN/DEFMACRO: redefining function BREAK in > /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, > was defined in /builddir/clisp-2.49/src/condition.fas > WARNING: Replacing method #)> in > # > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... > WARNING: The generic function # > is being modified, but has already been called. > WARNING: The generic function # > is being modified, but has already been called. > WARNING: The generic function # > is being modified, but has already been called. > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas > 0 errors, 5 warnings > ;; Swank started at port: 41975. > CL-USER> > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ... > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ... > WARNING: The generic function > # is being modified, > but has already been called. > WARNING: Replacing method > # (# (EQL :FIND-EXISTING))> > in # > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ... > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ... > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas ... > WARNING: Test failed: (&KEY #'#'+) => "(&key (function #'+))" > Expected: One of: "(&key (function #'+))", "(&key (function (function > +)))" > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas > > Process inferior-lisp segmentation fault > > --- buffer ends --- > > More information: > > - starting clisp in a terminal all on its own seems to work fine; I haven't had segmentation faults using it in isolation from slime. > > - I tried to start the server from within clisp and connect to it: > > (a) rlwrap clisp > (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") > (c) (swank-loader::init :reload t) > (d) (swank:create-server :port 7000) > (e) from within emacs: M-x slime-connect with localhost and port 7000 > > Same behavior as before: I get connected, get to make a few evaluations, get disconnected. > > This time around rlwrap tells me (in the terminal where I started clisp): > > rlwrap: warning: clisp crashed, killed by SIGSEGV > From achirvasub at gmail.com Tue Jul 23 13:59:39 2019 From: achirvasub at gmail.com (Stuart Little) Date: Tue, 23 Jul 2019 09:59:39 -0400 Subject: slime + clisp + emacs: server disconnects In-Reply-To: References: <20190723132910.GB9426@chirva-void> Message-ID: <20190723135939.GC9426@chirva-void> On Tue, Jul 23, 2019 at 04:52:00PM +0300, Stas Boukarev wrote: > It says that Clisp crashes with a segfault, nothing to do with slime. > It does say that, but a follow-up: If I run through the procedure described at the end, of starting swank from within clisp, there are no crashes with swank-v2.20 (rather than 2.24). I do get a warning in emacs to the effect that swank (2.20) and slime (2.24) versions don't match, but once I confirm that the crashes go away. So this same clisp installation works fine with swank 2.20 and not swank 2.24, meaning that some change in the latter is what's causing this. > On Tue, Jul 23, 2019 at 4:30 PM Stuart Little wrote: > > > > I am running > > > > - emacs 26.2 > > - slime 2.24 > > - clisp 2.49 > > > > on Linux. > > > > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > > > Lisp connection closed unexpectedly: connection broken by remote peer > > > > The inferior-lisp buffer reads as follows after the disconnect: > > > > --- buffer starts --- > > > > (progn (load "/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) > > > > i i i i i i i ooooo o ooooooo ooooo ooooo > > I I I I I I I 8 8 8 8 8 o 8 8 > > I \ `+' / I 8 8 8 8 8 8 > > \ `-+-' / 8 8 8 ooooo 8oooo > > `-__|__-' 8 8 8 8 8 > > | 8 o 8 8 o 8 8 > > ------+------ ooooo 8oooooo ooo8ooo ooooo 8 > > > > Welcome to GNU CLISP 2.49 (2010-07-07) > > > > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 > > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 > > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 > > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 > > Copyright (c) Sam Steingold, Bruno Haible 2001-2010 > > > > Type :h and hit Enter for context help. > > > > [1]> > > ;; Loading file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ... > > ;; Loaded file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ... > > WARNING: DEFUN/DEFMACRO: redefining function BREAK in > > /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, > > was defined in /builddir/clisp-2.49/src/condition.fas > > WARNING: Replacing method #)> in > > # > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... > > WARNING: The generic function # > > is being modified, but has already been called. > > WARNING: The generic function # > > is being modified, but has already been called. > > WARNING: The generic function # > > is being modified, but has already been called. > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas > > 0 errors, 5 warnings > > ;; Swank started at port: 41975. > > CL-USER> > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ... > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ... > > WARNING: The generic function > > # is being modified, > > but has already been called. > > WARNING: Replacing method > > # > (# (EQL :FIND-EXISTING))> > > in # > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ... > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ... > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas ... > > WARNING: Test failed: (&KEY #'#'+) => "(&key (function #'+))" > > Expected: One of: "(&key (function #'+))", "(&key (function (function > > +)))" > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas > > > > Process inferior-lisp segmentation fault > > > > --- buffer ends --- > > > > More information: > > > > - starting clisp in a terminal all on its own seems to work fine; I haven't had segmentation faults using it in isolation from slime. > > > > - I tried to start the server from within clisp and connect to it: > > > > (a) rlwrap clisp > > (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") > > (c) (swank-loader::init :reload t) > > (d) (swank:create-server :port 7000) > > (e) from within emacs: M-x slime-connect with localhost and port 7000 > > > > Same behavior as before: I get connected, get to make a few evaluations, get disconnected. > > > > This time around rlwrap tells me (in the terminal where I started clisp): > > > > rlwrap: warning: clisp crashed, killed by SIGSEGV > > From stassats at gmail.com Tue Jul 23 14:03:19 2019 From: stassats at gmail.com (Stas Boukarev) Date: Tue, 23 Jul 2019 17:03:19 +0300 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <20190723135939.GC9426@chirva-void> References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> Message-ID: Well, your clisp just happens to crash on that. On Tue, Jul 23, 2019 at 4:59 PM Stuart Little wrote: > > On Tue, Jul 23, 2019 at 04:52:00PM +0300, Stas Boukarev wrote: > > It says that Clisp crashes with a segfault, nothing to do with slime. > > > > It does say that, but a follow-up: > > If I run through the procedure described at the end, of starting swank from within clisp, there are no crashes with swank-v2.20 (rather than 2.24). > > I do get a warning in emacs to the effect that swank (2.20) and slime (2.24) versions don't match, but once I confirm that the crashes go away. > > So this same clisp installation works fine with swank 2.20 and not swank 2.24, meaning that some change in the latter is what's causing this. > > > On Tue, Jul 23, 2019 at 4:30 PM Stuart Little wrote: > > > > > > I am running > > > > > > - emacs 26.2 > > > - slime 2.24 > > > - clisp 2.49 > > > > > > on Linux. > > > > > > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > > > > > Lisp connection closed unexpectedly: connection broken by remote peer > > > > > > The inferior-lisp buffer reads as follows after the disconnect: > > > > > > --- buffer starts --- > > > > > > (progn (load "/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) > > > > > > i i i i i i i ooooo o ooooooo ooooo ooooo > > > I I I I I I I 8 8 8 8 8 o 8 8 > > > I \ `+' / I 8 8 8 8 8 8 > > > \ `-+-' / 8 8 8 ooooo 8oooo > > > `-__|__-' 8 8 8 8 8 > > > | 8 o 8 8 o 8 8 > > > ------+------ ooooo 8oooooo ooo8ooo ooooo 8 > > > > > > Welcome to GNU CLISP 2.49 (2010-07-07) > > > > > > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 > > > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 > > > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 > > > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 > > > Copyright (c) Sam Steingold, Bruno Haible 2001-2010 > > > > > > Type :h and hit Enter for context help. > > > > > > [1]> > > > ;; Loading file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ... > > > ;; Loaded file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ... > > > WARNING: DEFUN/DEFMACRO: redefining function BREAK in > > > /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, > > > was defined in /builddir/clisp-2.49/src/condition.fas > > > WARNING: Replacing method #)> in > > > # > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... > > > WARNING: The generic function # > > > is being modified, but has already been called. > > > WARNING: The generic function # > > > is being modified, but has already been called. > > > WARNING: The generic function # > > > is being modified, but has already been called. > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas > > > 0 errors, 5 warnings > > > ;; Swank started at port: 41975. > > > CL-USER> > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ... > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ... > > > WARNING: The generic function > > > # is being modified, > > > but has already been called. > > > WARNING: Replacing method > > > # > > (# (EQL :FIND-EXISTING))> > > > in # > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ... > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ... > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas ... > > > WARNING: Test failed: (&KEY #'#'+) => "(&key (function #'+))" > > > Expected: One of: "(&key (function #'+))", "(&key (function (function > > > +)))" > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas > > > > > > Process inferior-lisp segmentation fault > > > > > > --- buffer ends --- > > > > > > More information: > > > > > > - starting clisp in a terminal all on its own seems to work fine; I haven't had segmentation faults using it in isolation from slime. > > > > > > - I tried to start the server from within clisp and connect to it: > > > > > > (a) rlwrap clisp > > > (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") > > > (c) (swank-loader::init :reload t) > > > (d) (swank:create-server :port 7000) > > > (e) from within emacs: M-x slime-connect with localhost and port 7000 > > > > > > Same behavior as before: I get connected, get to make a few evaluations, get disconnected. > > > > > > This time around rlwrap tells me (in the terminal where I started clisp): > > > > > > rlwrap: warning: clisp crashed, killed by SIGSEGV > > > From achirvasub at gmail.com Tue Jul 23 14:50:05 2019 From: achirvasub at gmail.com (Stuart Little) Date: Tue, 23 Jul 2019 10:50:05 -0400 Subject: slime + clisp + emacs: server disconnects In-Reply-To: References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> Message-ID: <20190723145005.GD9426@chirva-void> On Tue, Jul 23, 2019 at 05:03:19PM +0300, Stas Boukarev wrote: > Well, your clisp just happens to crash on that. > I understand that :), but the purpose was to gain some insight into how or why it's happening. Perhaps I can hack the swank loading procedure to avoid this, for instance.But I'd need to understand the situation beyond the simple observation that there's a crash, hence the mailing list message. > On Tue, Jul 23, 2019 at 4:59 PM Stuart Little wrote: > > > > On Tue, Jul 23, 2019 at 04:52:00PM +0300, Stas Boukarev wrote: > > > It says that Clisp crashes with a segfault, nothing to do with slime. > > > > > > > It does say that, but a follow-up: > > > > If I run through the procedure described at the end, of starting swank from within clisp, there are no crashes with swank-v2.20 (rather than 2.24). > > > > I do get a warning in emacs to the effect that swank (2.20) and slime (2.24) versions don't match, but once I confirm that the crashes go away. > > > > So this same clisp installation works fine with swank 2.20 and not swank 2.24, meaning that some change in the latter is what's causing this. > > > > > On Tue, Jul 23, 2019 at 4:30 PM Stuart Little wrote: > > > > > > > > I am running > > > > > > > > - emacs 26.2 > > > > - slime 2.24 > > > > - clisp 2.49 > > > > > > > > on Linux. > > > > > > > > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > > > > > > > Lisp connection closed unexpectedly: connection broken by remote peer > > > > > > > > The inferior-lisp buffer reads as follows after the disconnect: > > > > > > > > --- buffer starts --- > > > > > > > > (progn (load "/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) > > > > > > > > i i i i i i i ooooo o ooooooo ooooo ooooo > > > > I I I I I I I 8 8 8 8 8 o 8 8 > > > > I \ `+' / I 8 8 8 8 8 8 > > > > \ `-+-' / 8 8 8 ooooo 8oooo > > > > `-__|__-' 8 8 8 8 8 > > > > | 8 o 8 8 o 8 8 > > > > ------+------ ooooo 8oooooo ooo8ooo ooooo 8 > > > > > > > > Welcome to GNU CLISP 2.49 (2010-07-07) > > > > > > > > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 > > > > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 > > > > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 > > > > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 > > > > Copyright (c) Sam Steingold, Bruno Haible 2001-2010 > > > > > > > > Type :h and hit Enter for context help. > > > > > > > > [1]> > > > > ;; Loading file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ... > > > > ;; Loaded file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ... > > > > WARNING: DEFUN/DEFMACRO: redefining function BREAK in > > > > /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, > > > > was defined in /builddir/clisp-2.49/src/condition.fas > > > > WARNING: Replacing method #)> in > > > > # > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... > > > > WARNING: The generic function # > > > > is being modified, but has already been called. > > > > WARNING: The generic function # > > > > is being modified, but has already been called. > > > > WARNING: The generic function # > > > > is being modified, but has already been called. > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas > > > > 0 errors, 5 warnings > > > > ;; Swank started at port: 41975. > > > > CL-USER> > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ... > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ... > > > > WARNING: The generic function > > > > # is being modified, > > > > but has already been called. > > > > WARNING: Replacing method > > > > # > > > (# (EQL :FIND-EXISTING))> > > > > in # > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ... > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ... > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas ... > > > > WARNING: Test failed: (&KEY #'#'+) => "(&key (function #'+))" > > > > Expected: One of: "(&key (function #'+))", "(&key (function (function > > > > +)))" > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas > > > > > > > > Process inferior-lisp segmentation fault > > > > > > > > --- buffer ends --- > > > > > > > > More information: > > > > > > > > - starting clisp in a terminal all on its own seems to work fine; I haven't had segmentation faults using it in isolation from slime. > > > > > > > > - I tried to start the server from within clisp and connect to it: > > > > > > > > (a) rlwrap clisp > > > > (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") > > > > (c) (swank-loader::init :reload t) > > > > (d) (swank:create-server :port 7000) > > > > (e) from within emacs: M-x slime-connect with localhost and port 7000 > > > > > > > > Same behavior as before: I get connected, get to make a few evaluations, get disconnected. > > > > > > > > This time around rlwrap tells me (in the terminal where I started clisp): > > > > > > > > rlwrap: warning: clisp crashed, killed by SIGSEGV > > > > From stassats at gmail.com Tue Jul 23 14:50:55 2019 From: stassats at gmail.com (Stas Boukarev) Date: Tue, 23 Jul 2019 17:50:55 +0300 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <20190723145005.GD9426@chirva-void> References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> <20190723145005.GD9426@chirva-void> Message-ID: Well, it's not slime that's crashing, so, can't really help with clisp problems. On Tue, Jul 23, 2019 at 5:50 PM Stuart Little wrote: > > On Tue, Jul 23, 2019 at 05:03:19PM +0300, Stas Boukarev wrote: > > Well, your clisp just happens to crash on that. > > > > I understand that :), but the purpose was to gain some insight into how or why it's happening. > > Perhaps I can hack the swank loading procedure to avoid this, for instance.But I'd need to understand the situation beyond the simple observation that there's a crash, hence the mailing list message. > > > On Tue, Jul 23, 2019 at 4:59 PM Stuart Little wrote: > > > > > > On Tue, Jul 23, 2019 at 04:52:00PM +0300, Stas Boukarev wrote: > > > > It says that Clisp crashes with a segfault, nothing to do with slime. > > > > > > > > > > It does say that, but a follow-up: > > > > > > If I run through the procedure described at the end, of starting swank from within clisp, there are no crashes with swank-v2.20 (rather than 2.24). > > > > > > I do get a warning in emacs to the effect that swank (2.20) and slime (2.24) versions don't match, but once I confirm that the crashes go away. > > > > > > So this same clisp installation works fine with swank 2.20 and not swank 2.24, meaning that some change in the latter is what's causing this. > > > > > > > On Tue, Jul 23, 2019 at 4:30 PM Stuart Little wrote: > > > > > > > > > > I am running > > > > > > > > > > - emacs 26.2 > > > > > - slime 2.24 > > > > > - clisp 2.49 > > > > > > > > > > on Linux. > > > > > > > > > > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > > > > > > > > > Lisp connection closed unexpectedly: connection broken by remote peer > > > > > > > > > > The inferior-lisp buffer reads as follows after the disconnect: > > > > > > > > > > --- buffer starts --- > > > > > > > > > > (progn (load "/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) > > > > > > > > > > i i i i i i i ooooo o ooooooo ooooo ooooo > > > > > I I I I I I I 8 8 8 8 8 o 8 8 > > > > > I \ `+' / I 8 8 8 8 8 8 > > > > > \ `-+-' / 8 8 8 ooooo 8oooo > > > > > `-__|__-' 8 8 8 8 8 > > > > > | 8 o 8 8 o 8 8 > > > > > ------+------ ooooo 8oooooo ooo8ooo ooooo 8 > > > > > > > > > > Welcome to GNU CLISP 2.49 (2010-07-07) > > > > > > > > > > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 > > > > > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 > > > > > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 > > > > > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 > > > > > Copyright (c) Sam Steingold, Bruno Haible 2001-2010 > > > > > > > > > > Type :h and hit Enter for context help. > > > > > > > > > > [1]> > > > > > ;; Loading file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ... > > > > > ;; Loaded file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ... > > > > > WARNING: DEFUN/DEFMACRO: redefining function BREAK in > > > > > /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, > > > > > was defined in /builddir/clisp-2.49/src/condition.fas > > > > > WARNING: Replacing method #)> in > > > > > # > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... > > > > > WARNING: The generic function # > > > > > is being modified, but has already been called. > > > > > WARNING: The generic function # > > > > > is being modified, but has already been called. > > > > > WARNING: The generic function # > > > > > is being modified, but has already been called. > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas > > > > > 0 errors, 5 warnings > > > > > ;; Swank started at port: 41975. > > > > > CL-USER> > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ... > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ... > > > > > WARNING: The generic function > > > > > # is being modified, > > > > > but has already been called. > > > > > WARNING: Replacing method > > > > > # > > > > (# (EQL :FIND-EXISTING))> > > > > > in # > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ... > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ... > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas > > > > > ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas ... > > > > > WARNING: Test failed: (&KEY #'#'+) => "(&key (function #'+))" > > > > > Expected: One of: "(&key (function #'+))", "(&key (function (function > > > > > +)))" > > > > > ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas > > > > > > > > > > Process inferior-lisp segmentation fault > > > > > > > > > > --- buffer ends --- > > > > > > > > > > More information: > > > > > > > > > > - starting clisp in a terminal all on its own seems to work fine; I haven't had segmentation faults using it in isolation from slime. > > > > > > > > > > - I tried to start the server from within clisp and connect to it: > > > > > > > > > > (a) rlwrap clisp > > > > > (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") > > > > > (c) (swank-loader::init :reload t) > > > > > (d) (swank:create-server :port 7000) > > > > > (e) from within emacs: M-x slime-connect with localhost and port 7000 > > > > > > > > > > Same behavior as before: I get connected, get to make a few evaluations, get disconnected. > > > > > > > > > > This time around rlwrap tells me (in the terminal where I started clisp): > > > > > > > > > > rlwrap: warning: clisp crashed, killed by SIGSEGV > > > > > From luismbo at gmail.com Tue Jul 23 14:59:38 2019 From: luismbo at gmail.com (=?UTF-8?Q?Lu=C3=ADs_Oliveira?=) Date: Tue, 23 Jul 2019 15:59:38 +0100 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <20190723145005.GD9426@chirva-void> References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> <20190723145005.GD9426@chirva-void> Message-ID: On Tue, Jul 23, 2019 at 3:51 PM Stuart Little wrote: > I understand that :), but the purpose was to gain some insight into how or why it's happening. Could you try and use git bisect to find what's upsetting your clisp? Luís From achirvasub at gmail.com Tue Jul 23 15:07:10 2019 From: achirvasub at gmail.com (A.C.) Date: Tue, 23 Jul 2019 18:07:10 +0300 Subject: slime + clisp + emacs: server disconnects In-Reply-To: References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> <20190723145005.GD9426@chirva-void> Message-ID: <7AB2C397-5D64-417A-B2CC-795EF9D06650@gmail.com> I'll try that when I get some time and get back to this list if / when there's anything to report. On July 23, 2019 5:59:38 PM GMT+03:00, "Luís Oliveira" wrote: >On Tue, Jul 23, 2019 at 3:51 PM Stuart Little >wrote: >> I understand that :), but the purpose was to gain some insight into >how or why it's happening. > >Could you try and use git bisect to find what's upsetting your clisp? > >Luís -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From achirvasub at gmail.com Tue Jul 23 15:37:34 2019 From: achirvasub at gmail.com (Stuart Little) Date: Tue, 23 Jul 2019 11:37:34 -0400 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <7AB2C397-5D64-417A-B2CC-795EF9D06650@gmail.com> References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> <20190723145005.GD9426@chirva-void> <7AB2C397-5D64-417A-B2CC-795EF9D06650@gmail.com> Message-ID: <20190723153734.GE9426@chirva-void> On Tue, Jul 23, 2019 at 06:07:10PM +0300, A.C. wrote: > I'll try that when I get some time and get back to this list if / when there's anything to report. > Done! Here's the report from git-bisect (it's somewhere between v2.20 and v2.21): --- cut --- 2e7f94633acebd5cf4074ce9601b021624ad8233 is the first bad commit commit 2e7f94633acebd5cf4074ce9601b021624ad8233 Author: Stas Boukarev Date: Thu Jan 11 15:29:00 2018 +0300 More energy efficient auto-flush-loop. Don't spin until there's something to flush. contrib/swank-repl.lisp | 8 +++++--- swank.lisp | 4 +++- swank/gray.lisp | 21 +++++++++++++++++---- 3 files changed, 25 insertions(+), 8 deletions(-) --- cut --- > On July 23, 2019 5:59:38 PM GMT+03:00, "Luís Oliveira" wrote: > >On Tue, Jul 23, 2019 at 3:51 PM Stuart Little > >wrote: > >> I understand that :), but the purpose was to gain some insight into > >how or why it's happening. > > > >Could you try and use git bisect to find what's upsetting your clisp? > > > >Luís > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. From achirvasub at gmail.com Tue Jul 23 16:04:34 2019 From: achirvasub at gmail.com (A.C.) Date: Tue, 23 Jul 2019 19:04:34 +0300 Subject: slime + clisp + emacs: server disconnects In-Reply-To: References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> <20190723145005.GD9426@chirva-void> Message-ID: I have sbcl too (switched to it after the clisp shenanigans started upon upgrading to v2.24): It does *not* crash, and I'm perfectly happy using sbcl. I was just impelled by curiosity to try and figure out what's wrong on the clisp side. On July 23, 2019 6:58:55 PM GMT+03:00, Michael Rice wrote: >Have you considered switching to Steel Bank Common Lisp (SBCL) to see >if it >also crashes? > >On Tue, Jul 23, 2019 at 10:51 AM Stuart Little >wrote: > >> On Tue, Jul 23, 2019 at 05:03:19PM +0300, Stas Boukarev wrote: >> > Well, your clisp just happens to crash on that. >> > >> >> I understand that :), but the purpose was to gain some insight into >how or >> why it's happening. >> >> Perhaps I can hack the swank loading procedure to avoid this, for >> instance.But I'd need to understand the situation beyond the simple >> observation that there's a crash, hence the mailing list message. >> >> > On Tue, Jul 23, 2019 at 4:59 PM Stuart Little > >> wrote: >> > > >> > > On Tue, Jul 23, 2019 at 04:52:00PM +0300, Stas Boukarev wrote: >> > > > It says that Clisp crashes with a segfault, nothing to do with >slime. >> > > > >> > > >> > > It does say that, but a follow-up: >> > > >> > > If I run through the procedure described at the end, of starting >swank >> from within clisp, there are no crashes with swank-v2.20 (rather than >2.24). >> > > >> > > I do get a warning in emacs to the effect that swank (2.20) and >slime >> (2.24) versions don't match, but once I confirm that the crashes go >away. >> > > >> > > So this same clisp installation works fine with swank 2.20 and >not >> swank 2.24, meaning that some change in the latter is what's causing >this. >> > > >> > > > On Tue, Jul 23, 2019 at 4:30 PM Stuart Little > >> wrote: >> > > > > >> > > > > I am running >> > > > > >> > > > > - emacs 26.2 >> > > > > - slime 2.24 >> > > > > - clisp 2.49 >> > > > > >> > > > > on Linux. >> > > > > >> > > > > Running M-x slime in emacs with 'inferior-lisp-program' set >to >> 'clisp' starts slime fine. I can usually run one evaluation (like say >(+ 2 >> 3)), whereupon any other action (pressing 'enter', say) will result >in a >> disconnect: >> > > > > >> > > > > Lisp connection closed unexpectedly: connection broken by >remote >> peer >> > > > > >> > > > > The inferior-lisp buffer reads as follows after the >disconnect: >> > > > > >> > > > > --- buffer starts --- >> > > > > >> > > > > (progn (load >> >"/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" >> :verbose t) (funcall (read-from-string "swank-loader:init") >:from-emacs t) >> (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) >> > > > > >> > > > > i i i i i i i ooooo o ooooooo ooooo >ooooo >> > > > > I I I I I I I 8 8 8 8 8 o 8 > 8 >> > > > > I \ `+' / I 8 8 8 8 8 > 8 >> > > > > \ `-+-' / 8 8 8 ooooo >8oooo >> > > > > `-__|__-' 8 8 8 8 8 >> > > > > | 8 o 8 8 o 8 8 >> > > > > ------+------ ooooo 8oooooo ooo8ooo ooooo 8 >> > > > > >> > > > > Welcome to GNU CLISP 2.49 (2010-07-07) > >> > > > > >> > > > > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 >> > > > > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 >> > > > > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold >1998 >> > > > > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 >> > > > > Copyright (c) Sam Steingold, Bruno Haible 2001-2010 >> > > > > >> > > > > Type :h and hit Enter for context help. >> > > > > >> > > > > [1]> >> > > > > ;; Loading file >> >/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas >... >> > > > > WARNING: DEFUN/DEFMACRO: redefining function BREAK in >> > > > > >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, >> > > > > was defined in >/builddir/clisp-2.49/src/condition.fas >> > > > > WARNING: Replacing method #T>)> >> in >> > > > > # >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... >> > > > > WARNING: The generic function #> STREAM-LINE-COLUMN> >> > > > > is being modified, but has already been called. >> > > > > WARNING: The generic function #> STREAM-FORCE-OUTPUT> >> > > > > is being modified, but has already been called. >> > > > > WARNING: The generic function #> STREAM-LINE-COLUMN> >> > > > > is being modified, but has already been called. >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas >> > > > > 0 errors, 5 warnings >> > > > > ;; Swank started at port: 41975. >> > > > > CL-USER> >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas >> ... >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas >> ... >> > > > > WARNING: The generic function >> > > > > # >is >> being modified, >> > > > > but has already been called. >> > > > > WARNING: Replacing method >> > > > > #> > > > > (# (EQL >> :FIND-EXISTING))> >> > > > > in #THREAD-FOR-EVALUATION> >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas >> ... >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas >> ... >> > > > > WARNING: Test failed: (&KEY #'#'+) => "(&key (function >#'+))" >> > > > > Expected: One of: "(&key (function #'+))", "(&key >> (function (function >> > > > > +)))" >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas >> > > > > >> > > > > Process inferior-lisp segmentation fault >> > > > > >> > > > > --- buffer ends --- >> > > > > >> > > > > More information: >> > > > > >> > > > > - starting clisp in a terminal all on its own seems to work >fine; >> I haven't had segmentation faults using it in isolation from slime. >> > > > > >> > > > > - I tried to start the server from within clisp and connect >to it: >> > > > > >> > > > > (a) rlwrap clisp >> > > > > (b) (load >> "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") >> > > > > (c) (swank-loader::init :reload t) >> > > > > (d) (swank:create-server :port 7000) >> > > > > (e) from within emacs: M-x slime-connect with localhost and >port >> 7000 >> > > > > >> > > > > Same behavior as before: I get connected, get to make a few >> evaluations, get disconnected. >> > > > > >> > > > > This time around rlwrap tells me (in the terminal where I >started >> clisp): >> > > > > >> > > > > rlwrap: warning: clisp crashed, killed by SIGSEGV >> > > > > >> >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pjb at informatimago.com Tue Jul 23 16:49:50 2019 From: pjb at informatimago.com (Pascal Bourguignon) Date: Tue, 23 Jul 2019 18:49:50 +0200 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <20190723132910.GB9426@chirva-void> References: <20190723132910.GB9426@chirva-void> Message-ID: <4BA7D145-C804-437A-A687-036E34174642@informatimago.com> > On 23 Jul 2019, at 15:29, Stuart Little wrote: > > I am running > > - emacs 26.2 > - slime 2.24 > - clisp 2.49 > > on Linux. > Works for me with - emacs 26.1 - slime 2.23 - clisp 2.49.93+ on Darwin and on Linux. > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > Lisp connection closed unexpectedly: connection broken by remote peer > Add a ~/.swank.lisp file with a line such as: #+clisp (defparameter swank:*use-dedicated-output-stream* nil) > > (a) rlwrap clisp rlwrap shouldn’t be needed with clisp, since it can be compiled with readline. This is the reason why clisp is GPL! > (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") > (c) (swank-loader::init :reload t) > (d) (swank:create-server :port 7000) > (e) from within emacs: M-x slime-connect with localhost and port 7000 > > Same behavior as before: I get connected, get to make a few evaluations, get disconnected. > > This time around rlwrap tells me (in the terminal where I started clisp): > > rlwrap: warning: clisp crashed, killed by SIGSEGV This should not occur. Since you don’t seem to have readline compiled in, perhaps you don’t have libsigsegv compiled in either? I would advise you to recompile clisp with those essential libraries! Have a look at the script I currently use to compile and install clisp from sources: https://github.com/informatimago/install/blob/master/install-pjb-environment#L399 Don’t use this script indiscriminately, it installs a lot of things!!! Instead, copy and paste what you need. -- __Pascal J. Bourguignon__ -------------- next part -------------- An HTML attachment was scrubbed... URL: From achirvasub at gmail.com Tue Jul 23 17:28:05 2019 From: achirvasub at gmail.com (Stuart Little) Date: Tue, 23 Jul 2019 13:28:05 -0400 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <4BA7D145-C804-437A-A687-036E34174642@informatimago.com> References: <20190723132910.GB9426@chirva-void> <4BA7D145-C804-437A-A687-036E34174642@informatimago.com> Message-ID: <20190723172805.GF9426@chirva-void> On Tue, Jul 23, 2019 at 06:49:50PM +0200, Pascal Bourguignon wrote: > > > On 23 Jul 2019, at 15:29, Stuart Little wrote: > > > > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > > > Lisp connection closed unexpectedly: connection broken by remote peer > > > > > Add a ~/.swank.lisp file with a line such as: > > #+clisp (defparameter swank:*use-dedicated-output-stream* nil) > This did not change anything in the slime+clisp behavior I described. > > > > > (a) rlwrap clisp > > rlwrap shouldn’t be needed with clisp, since it can be compiled with readline. This is the reason why clisp is GPL! > > > (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") > > (c) (swank-loader::init :reload t) > > (d) (swank:create-server :port 7000) > > (e) from within emacs: M-x slime-connect with localhost and port 7000 > > > > Same behavior as before: I get connected, get to make a few evaluations, get disconnected. > > > > This time around rlwrap tells me (in the terminal where I started clisp): > > > > rlwrap: warning: clisp crashed, killed by SIGSEGV > > This should not occur. > > > > Since you don’t seem to have readline compiled in, perhaps you don’t have libsigsegv compiled in either? > I would advise you to recompile clisp with those essential libraries! > > Have a look at the script I currently use to compile and install clisp from sources: > https://github.com/informatimago/install/blob/master/install-pjb-environment#L399 > Don’t use this script indiscriminately, it installs a lot of things!!! Instead, copy and paste what you need. > > > > -- > __Pascal J. Bourguignon__ > > > > From stassats at gmail.com Tue Jul 23 17:33:46 2019 From: stassats at gmail.com (Stas Boukarev) Date: Tue, 23 Jul 2019 20:33:46 +0300 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <20190723172805.GF9426@chirva-void> References: <20190723132910.GB9426@chirva-void> <4BA7D145-C804-437A-A687-036E34174642@informatimago.com> <20190723172805.GF9426@chirva-void> Message-ID: On Tue, Jul 23, 2019 at 8:29 PM Stuart Little wrote: > > On Tue, Jul 23, 2019 at 06:49:50PM +0200, Pascal Bourguignon wrote: > > > > > On 23 Jul 2019, at 15:29, Stuart Little wrote: > > > > > > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > > > > > Lisp connection closed unexpectedly: connection broken by remote peer > > > > > > > > > Add a ~/.swank.lisp file with a line such as: > > > > #+clisp (defparameter swank:*use-dedicated-output-stream* nil) > > > > This did not change anything in the slime+clisp behavior I described. It already defaults to NIL. From achirvasub at gmail.com Tue Jul 23 17:37:20 2019 From: achirvasub at gmail.com (Stuart Little) Date: Tue, 23 Jul 2019 13:37:20 -0400 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <4BA7D145-C804-437A-A687-036E34174642@informatimago.com> References: <20190723132910.GB9426@chirva-void> <4BA7D145-C804-437A-A687-036E34174642@informatimago.com> Message-ID: <20190723173720.GG9426@chirva-void> Oh, and regarding this: On Tue, Jul 23, 2019 at 06:49:50PM +0200, Pascal Bourguignon wrote: > Since you don’t seem to have readline compiled in, perhaps you don’t have libsigsegv compiled in either? > I don't have readline: starting plain 'clisp' (no rlwrap) produces ^[[A when pressing the up arrow, for instance. However, I do seem to have libsigsegv. Here's the full output of 'clisp --version': --- cut --- GNU CLISP 2.49 (2010-07-07) (built on build.voidlinux.eu [148.251.136.24]) Software: GNU C 6.2.1 20161126 cc -mtune=generic -O2 -pipe -g -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -O -DNO_SINGLEMAP -DNO_TRIVIALMAP -DENABLE_UNICODE -DNO_TERMCAP_NCURSES -DDYNAMIC_FFI -DNO_READLINE -I. -ldl /usr/lib/libavcall.a /usr/lib/libcallback.a -L/usr/lib -lsigsegv libgnu_cl.a SAFETY=0 TYPECODES WIDE_HARD SPVW_PAGES SPVW_MIXED libsigsegv 2.10 libffcall 1.11 Features: (REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES FFI GETTEXT UNICODE BASE-CHAR=CHARACTER WORD-SIZE=64 PC386 UNIX) C Modules: (clisp i18n syscalls regexp) Installation directory: /usr/lib/clisp-2.49/ User language: ENGLISH --- cut --- There's an '-lsigsegv' there.. > I would advise you to recompile clisp with those essential libraries! > > Have a look at the script I currently use to compile and install clisp from sources: > https://github.com/informatimago/install/blob/master/install-pjb-environment#L399 > Don’t use this script indiscriminately, it installs a lot of things!!! Instead, copy and paste what you need. > > > > -- > __Pascal J. Bourguignon__ > > > > From Joerg-Cyril.Hoehle at t-systems.com Wed Jul 24 13:41:39 2019 From: Joerg-Cyril.Hoehle at t-systems.com (Joerg-Cyril.Hoehle at t-systems.com) Date: Wed, 24 Jul 2019 13:41:39 +0000 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <20190723173720.GG9426@chirva-void> References: <20190723132910.GB9426@chirva-void> <4BA7D145-C804-437A-A687-036E34174642@informatimago.com> <20190723173720.GG9426@chirva-void> Message-ID: Hi, Stas Boukarev writes: >It says that Clisp crashes with a segfault, nothing to do with slime. This is only half of the truth. Ideally, clisp should not crash from a segmentation violation just by running Common Lisp code (it can crash when you modify the slots of internal objects used e.g. by its bytecode interpreter, but that doesn't count normally). OTOH, there are ways to make many programs die hard, involving sockets or pipes. E.g. consider this scenario: 0. Program binds *terminal-io*, *debug-io*, *standard-output* etc. to pipe or socket stream. 1. Program encounters simple exception and reports that over pipe. 2. Program at other end of pipe closes connection. 3. Program tries to write additional data (e.g. error message) to now closed pipe, causing yet another exception. 4. Possibly endless sequence of nested exceptions as the basic *error-output* and *debug-io* are unusable. 5. Stack overflow. SIGSEGV. Stuart has implicitly asked about how to have slime produce more trace output such that the origin of the SIGSEGV could be located in the application code. So far, I haven't seen an answer here. Stuart uses: >GNU CLISP 2.49 (2010-07-07) (built on build.voidlinux.eu [148.251.136.24]) I would recommend that you use clisp from 2017-2019, even though there has been no official release yet (it's still in the release candidate phase). There have been quite some robustness and portability enhancements in recent years. >However, I do seem to have libsigsegv. Here's the full output of 'clisp --version': >cc -mtune=generic -O2 -O [...] -DNO_SINGLEMAP -DNO_TRIVIALMAP -lsigsegv SAFETY=0 TYPECODES WIDE_HARD SPVW_PAGES SPVW_MIXED libsigsegv 2.10 libffcall 1.11 Without one of either SINGLEMAP_MEMORY or TRIVIALMAP_MEMORY you get no generational GC. Libsigsegv may still be used for stack overflow detection, I'm not sure. It appears to me that your build of clisp in voidlinux was done using overly pessimistic / conservative settings. With GC, you might be able to increase clisp's performance by 50%. You should recompile. (I can understand that distributions want to use very portable settings, but I think that's too much). Regards, Jörg Höhle From achirvasub at gmail.com Wed Jul 24 15:06:52 2019 From: achirvasub at gmail.com (Stuart Little) Date: Wed, 24 Jul 2019 11:06:52 -0400 Subject: slime + clisp + emacs: server disconnects In-Reply-To: References: <20190723132910.GB9426@chirva-void> <4BA7D145-C804-437A-A687-036E34174642@informatimago.com> <20190723173720.GG9426@chirva-void> Message-ID: <20190724150652.GH9426@chirva-void> Thank you! On Wed, Jul 24, 2019 at 01:41:39PM +0000, Joerg-Cyril.Hoehle at t-systems.com wrote: > Stuart uses: > >GNU CLISP 2.49 (2010-07-07) (built on build.voidlinux.eu [148.251.136.24]) > I would recommend that you use clisp from 2017-2019, even though there has been no official release yet (it's still in the release candidate phase). There have been quite some robustness and portability enhancements in recent years. > > >However, I do seem to have libsigsegv. Here's the full output of 'clisp --version': > >cc -mtune=generic -O2 -O [...] -DNO_SINGLEMAP -DNO_TRIVIALMAP -lsigsegv > SAFETY=0 TYPECODES WIDE_HARD SPVW_PAGES SPVW_MIXED libsigsegv 2.10 libffcall 1.11 > > Without one of either SINGLEMAP_MEMORY or TRIVIALMAP_MEMORY you get no generational GC. > Libsigsegv may still be used for stack overflow detection, I'm not sure. > > It appears to me that your build of clisp in voidlinux was done using overly pessimistic / conservative settings. With GC, you might be able to increase clisp's performance by 50%. You should recompile. > Done! The latest version I could find, cloned from mercurial[0] just minutes ago, does not crash. Well it did once, but not with a segfault, when I encountered an error. I'll keep monitoring it, but it's much better than before. The output from --version is --- cut --- GNU CLISP 2.49.93+ (2018-02-18) (built 3772968340) (memory 3772968415) Software: GNU C 9.1.0 gcc -g -O2 -no-integrated-cpp -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit -Wno-sign-compare -Wno-format-nonliteral -Wno-shift-negative-value -O -fwrapv -fno-strict-aliasing -DNO_ASM -DENABLE_UNICODE -DDYNAMIC_FFI -DDYNAMIC_MODULES libgnu.a -lreadline -lncurses -ldl -lffcall -lsigsegv SAFETY=0 HEAPCODES ONE_FREE_BIT_HEAPCODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.12 libreadline 8.0 libffcall 2.1 Features: (READLINE REGEXP WILDCARD SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER LOGICAL-PATHNAMES SOCKETS GENERIC-STREAMS SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER WORD-SIZE=64 PC386 UNIX) C Modules: (clisp i18n syscalls regexp readline) --- cut --- I didn't pass any special flags or anything, simply installed the dependencies they recommend in step 2 of [1] and proceeded as instructed there. --- References: [0] hg clone http://hg.code.sf.net/p/clisp/clisp [1] https://sourceforge.net/p/clisp/clisp/ci/tip/tree/unix/INSTALL From vas at oneofus.la Wed Jul 24 19:55:38 2019 From: vas at oneofus.la (Vladimir Sedach) Date: Wed, 24 Jul 2019 12:55:38 -0700 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <20190723145005.GD9426@chirva-void> References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> <20190723145005.GD9426@chirva-void> Message-ID: <87tvbbky11.fsf@t510.orion.oneofus.la> > Perhaps I can hack the swank loading procedure to avoid this, for > instance.But I'd need to understand the situation beyond the simple > observation that there's a crash, hence the mailing list message. If CLISP crashes because of a bad memory reference (SIGSEGV), then it is a problem with the internals of CLISP, which is triggered by SWANK only incidentally. Even if there is some workaround for loading SLIME, it will not be very useful, because CLISP will continue crashing on whatever code you want to work on. You need to trace down the point where it crashes by stepping through the SWANK code in the debugger (you can narrow it down quickly by putting break or print statements in the code in a binary search pattern), isolate the problem code in a self-contained, reproducible example, then try to debug the CLISP run-time, by re-compiling CLISP with run-time debugging support and using GDB/strace/the usual C debugging tools: https://clisp.sourceforge.io/impnotes/faq.html#faq-debug There is a CLISP mailing list where you can get more specific information: https://sourceforge.net/projects/clisp/lists/clisp-list Vladimir From achirvasub at gmail.com Thu Jul 25 05:29:39 2019 From: achirvasub at gmail.com (Stuart Little) Date: Thu, 25 Jul 2019 01:29:39 -0400 Subject: slime + clisp + emacs: server disconnects In-Reply-To: <87tvbbky11.fsf@t510.orion.oneofus.la> References: <20190723132910.GB9426@chirva-void> <20190723135939.GC9426@chirva-void> <20190723145005.GD9426@chirva-void> <87tvbbky11.fsf@t510.orion.oneofus.la> Message-ID: <20190725052939.GA4294@arch-chirva.localdomain> On Wed, Jul 24, 2019 at 12:55:38PM -0700, Vladimir Sedach wrote: > Even if there is some workaround for loading > SLIME, it will not be very useful, because CLISP will continue > crashing on whatever code you want to work on. > I see, thanks. > then try to debug the CLISP run-time, by re-compiling CLISP > with run-time debugging support and using GDB/strace/the usual C > debugging tools Well, if I'm recompiling anyway, I don't think it'll be profitable at this stage to do so just to debug the 10-year-old version of the program.. Compiling the latest (following Jörg's suggestion earlier in the thread) eliminates the crashes, as reported above. I've since discovered that the version that comes with arch linux doesn't crash either: --- cut --- GNU CLISP 2.49.93+ (2018-02-18) (built on felixonmars2 [163.172.20.151]) Software: GNU C 8.2.1 20181127 gcc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -no-integrated-cpp -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit -Wno-sign-compare -Wno-format-nonliteral -Wno-shift-negative-value -O -fwrapv -fno-strict-aliasing -DNO_ASM -DENABLE_UNICODE -DDYNAMIC_FFI -DDYNAMIC_MODULES -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now libgnu.a /usr/lib/libreadline.so -lncurses -ldl /usr/lib/libavcall.a /usr/lib/libcallback.a /usr/lib/libsigsegv.so /usr/lib/libunistring.so SAFETY=0 HEAPCODES ONE_FREE_BIT_HEAPCODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.12 libreadline 8.0 libffcall 1.13 Features: (READLINE REGEXP WILDCARD SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER LOGICAL-PATHNAMES SOCKETS GENERIC-STREAMS SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER WORD-SIZE=64 PC386 UNIX) C Modules: (clisp i18n syscalls regexp readline) Installation directory: /usr/lib/clisp-2.49.93+/ --- cut --- This is on the same machine, booting a different distro (arch as opposed to void). > : > > https://clisp.sourceforge.io/impnotes/faq.html#faq-debug > > There is a CLISP mailing list where you can get more specific > information: > > https://sourceforge.net/projects/clisp/lists/clisp-list > > Vladimir