/[slime]/slime/PROBLEMS
ViewVC logotype

Contents of /slime/PROBLEMS

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.9 - (show annotations)
Sat Dec 3 13:06:50 2011 UTC (2 years, 4 months ago) by heller
Branch: MAIN
CVS Tags: HEAD
Changes since 1.8: +8 -9 lines
Mention problem with CLISP Windows filenames.
1 Known problems with SLIME -*- outline -*-
2
3 * Common to all backends
4
5 ** Caution: network security
6
7 The `M-x slime' command has Lisp listen on a TCP socket and wait for
8 Emacs to connect, which typically takes on the order of one second. If
9 someone else were to connect to this socket then they could use the
10 SLIME protocol to control the Lisp process.
11
12 The listen socket is bound on the loopback interface in all Lisps that
13 support this. This way remote hosts are unable to connect.
14
15 ** READ-CHAR-NO-HANG is broken
16
17 READ-CHAR-NO-HANG doesn't work properly for slime-input-streams. Due
18 to the way we request input from Emacs it's not possible to repeatedly
19 poll for input. To get any input you have to call READ-CHAR (or a
20 function which calls READ-CHAR).
21
22 * Backend-specific problems
23
24 ** CMUCL
25
26 The default communication style :SIGIO is reportedly unreliable with
27 certain libraries (like libSDL) and certain platforms (like Solaris on
28 Sparc). It generally works very well on x86 so it remains the default.
29
30 ** SBCL
31
32 The latest released version of SBCL at the time of packaging should
33 work. Older or newer SBCLs may or may not work. Do not use
34 multithreading with unpatched 2.4 Linux kernels. There are also
35 problems with kernel versions 2.6.5 - 2.6.10.
36
37 The (v)iew-source command in the debugger can only locate exact source
38 forms for code compiled at (debug 2) or higher. The default level is
39 lower and SBCL itself is compiled at a lower setting. Thus only
40 defun-granularity is available with default policies.
41
42 ** LispWorks
43
44 On Windows, SLIME hangs when calling foreign functions or certain
45 other functions. The reason for this problem is unknown.
46
47 We only support latin1 encoding. (Unicode wouldn't be hard to add.)
48
49 ** Allegro CL
50
51 Interrupting Allegro with C-c C-b can be slow. This is caused by the
52 a relatively large process-quantum: 2 seconds by default. Allegro
53 responds much faster if mp:*default-process-quantum* is set to 0.1.
54
55 ** CLISP
56
57 We require version 2.49 or higher. We also require socket support, so
58 you may have to start CLISP with "clisp -K full".
59
60 Under Windows, interrupting (with C-c C-b) doesn't work. Emacs sends
61 a SIGINT signal, but the signal is either ignored or CLISP exits
62 immediately.
63
64 On Windows, CLISP may refuse to parse filenames like
65 "C:\\DOCUME~1\\johndoe\\LOCALS~1\\Temp\\slime.1424" when we actually
66 mean C:\Documents and Settings\johndoe\Local Settings\slime.1424. As
67 a workaround, you could set slime-to-lisp-filename-function to some
68 function that returns a string that is accepted by CLISP.
69
70 Function arguments and local variables aren't displayed properly in
71 the backtrace. Changes to CLISP's C code are needed to fix this
72 problem. Interpreted code is usually easer to debug.
73
74 M-. (find-definition) only works if the fasl file is in the same
75 directory as the source file.
76
77 The arglist doesn't include the proper names only "fake symbols" like
78 `arg1'.
79
80 ** Armed Bear Common Lisp
81
82 The ABCL support is still new and experimental.
83
84 ** Corman Common Lisp
85
86 We require version 2.51 or higher, with several patches (available at
87 http://www.grumblesmurf.org/lisp/corman-patches).
88
89 The only communication style currently supported is NIL.
90
91 Interrupting (with C-c C-b) doesn't work.
92
93 The tracing, stepping and XREF commands are not implemented along with
94 some debugger functionality.

  ViewVC Help
Powered by ViewVC 1.1.5