/[slime]/slime/PROBLEMS
ViewVC logotype

Contents of /slime/PROBLEMS

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.4 - (hide annotations)
Sun Mar 27 19:41:46 2005 UTC (9 years ago) by heller
Branch: MAIN
Changes since 1.3: +14 -15 lines
*** empty log message ***
1 lgorrie 1.1 Known problems with SLIME -*- outline -*-
2    
3     * Common to all backends
4    
5     ** Caution: network security
6     The `M-x slime' command has Lisp listen on a TCP socket and wait for
7     Emacs to connect, which typically takes on the order of one second. If
8     someone else were to connect to this socket then they could use the
9     SLIME protocol to control the Lisp process.
10    
11     The listen socket is bound on the loopback interface in all Lisps that
12     support this. This way remote hosts are unable to connect.
13    
14     * Backend-specific problems
15    
16     ** CMUCL
17    
18     The default communication style :SIGIO is reportedly unreliable with
19     certain libraries (like libSDL) and certain platforms (like Solaris on
20     Sparc). It generally works very well on x86 so it remains the default.
21    
22     ** SBCL
23    
24 heller 1.4 SBCL versions from 0.8.15 to 0.8.20 should work. Newer SBCL's may or
25     may not work.
26 lgorrie 1.1
27     The (v)iew-source command in the debugger can only locate exact source
28     forms for code compiled at (debug 2) or higher. The default level is
29     lower and SBCL itself is compiled at a lower setting. Thus only
30     defun-granularity is available with default policies.
31    
32     The XREF commands are not implemented.
33    
34     ** OpenMCL
35    
36 heller 1.4 We support OpenMCL 0.14.3.
37 lgorrie 1.1
38     The XREF commands are not available.
39    
40     ** LispWorks
41    
42 heller 1.4 On Windows, SLIME hangs when calling foreign functions or certain
43     other functions. The reason for this problem is unknown.
44    
45     We only support latin1 encoding. (Unicode wouldn't be hard to add.)
46 lgorrie 1.1
47     ** Allegro CL
48    
49 heller 1.2 Interrupting Allegro with C-c C-b can be slow. This is caused by the
50     a relatively large process-quantum: 2 seconds by default. Allegro
51     responds much faster if mp:*default-process-quantum* is set to 0.1.
52 lgorrie 1.1
53     ** CLISP
54    
55 heller 1.4 We require version 2.33.2 or higher. We also require socket support, so
56 lgorrie 1.1 you may have to start CLISP with "clisp -K full".
57    
58 heller 1.4 Under Windows, interrupting (with C-c C-b) doesn't work. Emacs sends
59     a signal 2 (= SIGINT), but the signal is either ignored or CLISP exits
60     immediately.
61    
62     The backtrace doesn't include frames for compiled functions. Changes
63     to CLISP's C code are needed to fix this problem.
64 lgorrie 1.1 Interpreted code is usually easer to debug.
65    
66     M-. (find-definition) only works if the fasl file is in the same
67     directory as the source file.
68    
69     ** Armed Bear Common Lisp
70    
71     The ABCL support is still new and experimental.
72    

  ViewVC Help
Powered by ViewVC 1.1.5