slime + clisp + emacs: server disconnects

[Stuart Little]

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