[slime-devel] swank+sbcl and cpu utilization

[Chris Goellner]

That does the trick on the CPU utilization. Thanks for the fix.

I commented out the (setf swank:*communication-style* :fd-handler). If
I used :sigio or :spawn I got an error.

The :sigio says:

The variable SB-POSIX:O-ASYNC is unbound.
   [Condition of type UNBOUND-VARIABLE]

when I connect with slime.

The :spawn says:

SWANK-BACKEND:SPAWN not implementated

when I try to run the remote swank. SBCL on Solaris doesn't seem to
have the same feature set as my Linux version.

But, with nothing set it works like a charm. Thanks again.

On Thu, Oct 30, 2008 at 5:33 AM, Helmut Eller <heller at common-lisp.net> wrote:
> * Chris Goellner [2008-10-29 03:05+0100] writes:
>
>> I'm trying to get a remote SWANK+SBCL setup going and I've hit a snag.
>> Everything works and I can connect to the running SBCL. However, when
>> I disconnect the SBCL process drives the CPU to 100%.
>
> This was caused by a bug.  It should be fixed in HEAD.
>
> Thanks for the report.
>
> Helmut.
>
>
> PS: If you use :fd-handler, slime-interrupt won't work on a remote
> machine.  That works only with :sigio and :spwan.
>
>
> _______________________________________________
> slime-devel site list
> slime-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/slime-devel
>