[Bese-devel] Problem using slime with sbcl and modlisp

[Marco Baringer]

Luigi Panzeri <matley at muppetslab.org> writes:

> I have a problem using sbcl 0.8.19 slime(from CVS) and ucw(0.3.7 or
> dev). Maybe this is a problem related to slime+modlisp(2.41 from
> debian), not to ucw. But i dont manage to reply this slime problem
> without ucw.
>
> Step to reproduce my problem:
> start ucw with example app (with init.lisp)
> signal an error with example app
> choose Show backtrace 
> try to use M-. somewhere
> my emacs/slime hangs

If you're using a single threaded lisp then the sldb buffer "blocks"
the slime/emacs communication channel, it could be that M-. is not
properly checking and is waiting for a response which can't come
(deadlock). does the repl respond? (can you eval nil or something
simple?) what happens if you chose a restart from the sldb menu?

> Other two minor question:
> 1) with 0.3.7 i note that link for debugging/inspecting component
> are rendered, how can i hide these?

(setf ucw:*inspect-components* nil)

or use the admin app. this used to default to NIL and I changed it
just recently, maybe i'll change it back.

> 2) i tried to use araneida (because i have ever got minor but
> blocking problems with modlisp), but i dont get response with my
> configuration. But i have the same problem with araneida example.

?

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen