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

Re: [slime-devel] slime & sbcl event-loop issues
by xristos 16 Feb '09

16 Feb '09

Ok problem solved, mostly. I updated slime from cvs and swank :fd-handler works now without me calling serve-event at all. Chris

1 0

[slime-devel] slime & sbcl event-loop issues
by xristos 15 Feb '09

15 Feb '09

I am trying to use serve-event to interactively monitor network protocols but i'm facing some issues when trying to work on the slime repl: 1) On threaded sbcl + :spawn swank comm style, serve-event does not run at all on the repl thread (the thread seems to be blocked on a call to condition-wait, in receive-if/swank-sbcl.lisp) I tried modifying receive-if so that it serves all pending events before acquiring the lock but i guess this could prove to be problematic. 2) Also tried scheduling a timer to interrupt *current-thread* (repl thread) and run serve-all-events periodically which works but i guess this is even worse than 1) and could explode pretty easy. 3) Using :fd-handler (and therefore a single thread) it seems that slime completely takes over the event loop and does not allow other handlers to run unless there is input coming from the repl. (Blocking on read-sequence ?) I could give up :spawn and work with :fd-handler comm style, if slime would let other handlers run and not block without configurable timeout at least. Is this feasible ? Where would one start looking in order to implement it ? Chris

2 3

[slime-devel] problem with debug-source-f[or|ro]m
by Vsevolod 13 Feb '09

13 Feb '09

Hi guys! I'm debugging a problem with slime startup on Windows, which symptom is this message on M-x slime: > Symbol "DEBUG-SOURCE-FROM" not found in the SB-DI package. > Curiously, when I skimmed through SBCL code, I didn't find any debug-source-fROm function, but have found debug-source-fORm. And in the slime sources the two even may be encountered side-by-side. I wonder, is it a coincidence or a typo, leading to a bug? Other unrelated question I've remembered. When I try to evaluate something in debugger process (with e <expr>), the slime connection dies (SBCL 1.0.20, Slime 2008-10-23, Debian GNU/Linux Etch). By chance, a common problem with a well-known solution? Thanks, Vsevolod

2 2

[slime-devel] Daily ChangeLog diff
by Helmut Eller 12 Feb '09

12 Feb '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1676 slime/ChangeLog:1.1678 --- slime/ChangeLog:1.1676 Sat Feb 7 13:19:50 2009 +++ slime/ChangeLog Wed Feb 11 20:55:01 2009 @@ -1,3 +1,20 @@ +2009-02-11 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-current-tlf, slime-current-form-path): New + functions; can be handy when inspecting source-locations while + debugging M-. + +2009-02-11 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el: Barf if emacs-major-version <= 20. We support 21 and up. + (slime-emacs-20-p): Removed. + + * slime.el (slime-forward-reader-comment): Removed. + (slime-forward-any-comment): New; superset of above. + (slime-forward-reader-conditional): Make it understand SBCL's + #!+,#!- so it works in source files of SBCL itself, too. + (slime-current-parser-state): New. + 2009-02-07 Tobias C. Rittweiler <tcr(a)freebits.de> In Xref, list IR1-conversion functions with :DEF-IR1-TRANSLATOR as

1 0

[slime-devel] SLIME Typeout stopped working?
by Jeff Cunningham 11 Feb '09

11 Feb '09

I just upgraded slime after not doing so in several months and *SLIME Typeout* immediately stopped working. The frame comes up blank but the output goes to the normal single line edit buffer at the bottom of the main frame. I'm running SBCL (very recent) and emacs 22. Has anyone else noticed this? Is there a fix? My .emacs setup is: (add-to-list 'load-path "/usr/src/clbuild/source/slime") (add-to-list 'load-path "/usr/src/clbuild/source/slime/contrib") (require 'slime) (slime-setup '(slime-fancy slime-typeout-frame slime-asdf slime-tramp)) (global-set-key "\C-cs" 'slime-selector) Thanks --Jeff Cunningham

2 1

[slime-devel] openmcl/ccl: Failed to join repl-thread - Exhausted
by David Reitter 11 Feb '09

11 Feb '09

I occasionally get "Failed to join #<PROCESS repl-thread(11) [Exhausted]" crashes of the Lisp process, using OpenMCL/CCL on OS X as the backend. (This is with Slime CVS 26 Jan). In this particular case, I had received a simple syntax error while compiling (C-c C-k), fixed it, and compiled again. I received no confirmation that the process had finished, so I checked the *inferior-lisp* buffer - contents below. Let me know if I can supply more information regarding this. PS.: Please cc me on replies. (progn (load "/Library/Application Support/Aquamacs Emacs/SLIME/swank- loader.lisp" :verbose t) (funcall (read-from-string "swank- loader:init")) (funcall (read-from-string "swank:start-server") "/var/ folders/8h/8hIgrExEHNOfZGhlNEY32k+++TI/-Tmp-/slime.25155" :coding- system "iso-latin-1-unix")) ; loading system definition from ccl:tools;asdf-install;asdf- install.asd.newest into #<Package "ASDF0"> ; registering #<SYSTEM ASDF-INSTALL #x300040D7D06D> as ASDF-INSTALL ;;; ASDF-Install version 0.6.10 Welcome to Clozure Common Lisp Version 1.2-r11300M (DarwinX8664)! ? ;Loading #P"/Library/Application Support/Aquamacs Emacs/SLIME/swank- loader.lisp"... ;Loading #P"/Users/dr/.slime/fasl/2009-01-23/openmcl-version_1.2- r11300m__(darwinx8664)-darwin-x86-64/swank-backend.dx64fsl"... ;Loading #P"/Users/dr/.slime/fasl/2009-01-23/openmcl-version_1.2- r11300m__(darwinx8664)-darwin-x86-64/metering.dx64fsl"... ;Loading #P"/Users/dr/.slime/fasl/2009-01-23/openmcl-version_1.2- r11300m__(darwinx8664)-darwin-x86-64/swank-openmcl.dx64fsl"... ;Loading #P"/Users/dr/.slime/fasl/2009-01-23/openmcl-version_1.2- r11300m__(darwinx8664)-darwin-x86-64/swank-gray.dx64fsl"... ;Loading #P"/Users/dr/.slime/fasl/2009-01-23/openmcl-version_1.2- r11300m__(darwinx8664)-darwin-x86-64/swank.dx64fsl"... ; Warning: These Swank interfaces are unimplemented: ; (ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER CALLS- WHO FIND-SOURCE-LOCATION MACROEXPAND-ALL REMOVE-FD-HANDLERS REMOVE- SIGIO-HANDLERS RESTART-FRAME RETURN-FROM-FRAME SAVE-IMAGE SLDB-BREAK- AT-START SLDB-BREAK-ON-RETURN SLDB-STEP-INTO SLDB-STEP-NEXT SLDB-STEP- OUT) ; While executing: SWANK-BACKEND::WARN-UNIMPLEMENTED-INTERFACES, in process listener(1). ;; Swank started at port: 57898. 57898 ? ;; swank:close-connection: Fault during read of memory address #x77A270 > Error: Failed to join #<PROCESS repl-thread(11) [Exhausted] #x300040F0EDBD> > While executing: #<CCL::STANDARD-KERNEL-METHOD CCL:JOIN-PROCESS (CCL:PROCESS)>, in process control-thread(3). ;;; ;;; #<PROCESS control-thread(3) [Active] #x300040EF3B4D> requires access to Shared Terminal Input ;;;

1 0

[slime-devel] Swank socket problem
by Cornelius Riemenschneider 08 Feb '09

08 Feb '09

Hi, I want to use swank together with the eclipse cusp plugin - so far so good. But when starting swank, I always get this error (from a manual session reproducing the problem) [corni@localhost slime]$ LC_ALL=C sbcl This is SBCL 1.0.21, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * (load "swank-loader.lisp") T * (swank-loader:init) ; loading #P"/home/corni/.slime/fasl/2009-02-07/sbcl-1.0.21-linux-x86/swank-backend.fasl" ; loading #P"/home/corni/.slime/fasl/2009-02-07/sbcl-1.0.21-linux-x86/swank-source-path-parser.fasl" ; loading #P"/home/corni/.slime/fasl/2009-02-07/sbcl-1.0.21-linux-x86/swank-source-file-cache.fasl" ; loading #P"/home/corni/.slime/fasl/2009-02-07/sbcl-1.0.21-linux-x86/swank-sbcl.fasl" STYLE-WARNING: redefining EMACS-INSPECT (#<BUILT-IN-CLASS T>) in DEFMETHOD ; loading #P"/home/corni/.slime/fasl/2009-02-07/sbcl-1.0.21-linux-x86/swank-gray.fasl" STYLE-WARNING: Implicitly creating new generic function STREAM-READ-CHAR-WILL-HANG-P. ; loading #P"/home/corni/.slime/fasl/2009-02-07/sbcl-1.0.21-linux-x86/swank.fasl" WARNING: These Swank interfaces are unimplemented: (CALLS-WHO DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN WHO-SPECIALIZES) NIL * (swank:create-server :port 12345) debugger invoked on a SB-BSD-SOCKETS:SOCKET-ERROR in thread #<THREAD "initial thread" RUNNING {AA1B639}>: Socket error in "bind": 99 (Cannot assign requested address) Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (SB-BSD-SOCKETS:SOCKET-ERROR "bind") 0] I've no idea what's causing this, can you help me? I'm on Linux, moblin (fedora related distro), 32bit. Cornelius

2 2

[slime-devel] Daily ChangeLog diff
by Helmut Eller 08 Feb '09

08 Feb '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1675 slime/ChangeLog:1.1676 --- slime/ChangeLog:1.1675 Fri Feb 6 23:48:14 2009 +++ slime/ChangeLog Sat Feb 7 13:19:50 2009 @@ -1,5 +1,14 @@ 2009-02-07 Tobias C. Rittweiler <tcr(a)freebits.de> + In Xref, list IR1-conversion functions with :DEF-IR1-TRANSLATOR as + prefix rather than DEFUN. (Test case: M-. on FUNCTION.) + + * swank-sbcl.lisp (definition-specifier): New function. + (make-dspec): New function. Splitted from + MAKE-SOURCE-LOCATION-SPECIFICATION. + +2009-02-07 Tobias C. Rittweiler <tcr(a)freebits.de> + * slime.el (slime-initialize-macroexpansion-buffer): Clear the buffer-undo-list, so the user can't get expansions from earlier macroexpansions into the buffer, screwing up badly.

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 07 Feb '09

07 Feb '09

Index: slime/ChangeLog diff -u slime/ChangeLog:1.1674 slime/ChangeLog:1.1675 --- slime/ChangeLog:1.1674 Fri Jan 30 09:58:48 2009 +++ slime/ChangeLog Fri Feb 6 23:48:14 2009 @@ -1,3 +1,9 @@ +2009-02-07 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-initialize-macroexpansion-buffer): Clear the + buffer-undo-list, so the user can't get expansions from earlier + macroexpansions into the buffer, screwing up badly. + 2009-01-30 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-clisp.lisp (fspec-location): Fix creation of source-location.

1 0

[slime-devel] Differences between hooks
by jcm＠sdf.lonestar.org 06 Feb '09

06 Feb '09

I'm tweaking my slime setup, and trying to understand some slime behavior. Would someone explain the difference between slime-LOAD-hook and slime-MODE-hook? I seem to have some bindings that only work correctly when set up inside one or the other hook.

2 1