Gabor Melis gabor.melis@essnet.se writes:
Hmm. Setting swank:*communication-style* to :spawn seems to work.
In this configuration, the debugger is executed in the correct thread, and the frame-pointer should point to the correct stack. But be warned, CMUCL's multithreading is non-preemptive, and interrupting will not work if a thread is busy executing an endless loop.
I thought that slime-multiprocessing implies :spawn but looking at the code I can see that's not the case.
That's true. Not sure if it should, because that would override any setting in the .swank.lisp file. What do you think?
On Wednesday 12 May 2004 16:36, Helmut Eller wrote:
Gabor Melis gabor.melis@essnet.se writes:
I thought that slime-multiprocessing implies :spawn but looking at the code I can see that's not the case.
That's true. Not sure if it should, because that would override any setting in the .swank.lisp file. What do you think?
It certainly looks a bit redundant. IMHO, after rereading the documentation :spawn should imply slime-multiprocessing (assuming there is legitimate use for slime-multiprocessing without :spawn).
-
Gabor Melis -
Helmut Eller