From: Jamie Border
Subject: UCW, SLIME and restarts
Date: 
Message-ID: <da8f9p$1dh$1@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com>
So I've got some stuff running in UCW 0.3.9 using the portableaserve 
backend, and CMUCL 19a.

Everything works great except:

* Using the ucw examples (/ucw/examples/index.ucw), if I click on 'Signal an 
Error', I get a pretty backtrace.

* If I do this with SLIME (1.2.1) connected, it starts sldb, but every 
restart I try seems to have no effect:

'Restart returned nil'

And the list of restarts sits there until I choose enough to make CMUCL tell 
me I have too many nested errors.

Am I missing something?

Jamie

From: svg
Subject: Re: UCW, SLIME and restarts
Date: 
Message-ID: <1120403648.811856.260600@o13g2000cwo.googlegroups.com>
> So I've got some stuff running in UCW 0.3.9 using the portableaserve
> backend, and CMUCL 19a.
>
> Everything works great except:
>
> * Using the ucw examples (/ucw/examples/index.ucw), if I click on 'Signal an
> Error', I get a pretty backtrace.
>
> * If I do this with SLIME (1.2.1) connected, it starts sldb, but every
> restart I try seems to have no effect:
>
> 'Restart returned nil'
>

Set swank:*communication-style* to :spawn. By default it is :sigio for
CMUCL and it
seems that UCW handler catches swank signal.

Best Regards,
Vladimir Sekissov
From: Jamie Border
Subject: Re: UCW, SLIME and restarts
Date: 
Message-ID: <dalmfd$kka$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com>
Did this, no joy.

Assembling good cut-and-paste now; watch this space.

"svg" <···@surnet.ru> wrote in message 
·····························@o13g2000cwo.googlegroups.com...
>
>
>> So I've got some stuff running in UCW 0.3.9 using the portableaserve
>> backend, and CMUCL 19a.
>>
>> Everything works great except:
>>
>> * Using the ucw examples (/ucw/examples/index.ucw), if I click on 'Signal 
>> an
>> Error', I get a pretty backtrace.
>>
>> * If I do this with SLIME (1.2.1) connected, it starts sldb, but every
>> restart I try seems to have no effect:
>>
>> 'Restart returned nil'
>>
>
> Set swank:*communication-style* to :spawn. By default it is :sigio for
> CMUCL and it
> seems that UCW handler catches swank signal.
>
> Best Regards,
> Vladimir Sekissov
> 
From: Jamie Border
Subject: Re: UCW, SLIME and restarts
Date: 
Message-ID: <daloc7$1ja$1@nwrdmz03.dmz.ncs.ea.ibs-infra.bt.com>
I took everything I thought would make a difference and put it at:

http://www.jborder.com/ephemeral/ucw-cmucl-dump.tar.gz

Perhaps this problem might not appear if I was using SBCL?

Jamie

"Jamie Border" <·····@jborder.com> wrote in message 
·················@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com...
> Did this, no joy.
>
> Assembling good cut-and-paste now; watch this space.
>
> "svg" <···@surnet.ru> wrote in message 
> ·····························@o13g2000cwo.googlegroups.com...
>>
>>
>>> So I've got some stuff running in UCW 0.3.9 using the portableaserve
>>> backend, and CMUCL 19a.
>>>
>>> Everything works great except:
>>>
>>> * Using the ucw examples (/ucw/examples/index.ucw), if I click on 
>>> 'Signal an
>>> Error', I get a pretty backtrace.
>>>
>>> * If I do this with SLIME (1.2.1) connected, it starts sldb, but every
>>> restart I try seems to have no effect:
>>>
>>> 'Restart returned nil'
>>>
>>
>> Set swank:*communication-style* to :spawn. By default it is :sigio for
>> CMUCL and it
>> seems that UCW handler catches swank signal.
>>
>> Best Regards,
>> Vladimir Sekissov
>>
>
> 
From: svg
Subject: Re: UCW, SLIME and restarts
Date: 
Message-ID: <1120831471.657565.236290@g14g2000cwa.googlegroups.com>
Good day,

You are setting swank:*communication-style* too late.
Use .swank.lisp in your home directory to customize swank behaviour.
From: Jamie Border
Subject: Re: UCW, SLIME and restarts
Date: 
Message-ID: <dam5ik$qk2$1@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com>
Thanks, Vladimir.

My ~/.swank.lisp now contains:

(setq swank:*communication-style* :spawn)

and this works perfectly.

Job done; well done c.l.l as usual!

Jamie


"svg" <···@surnet.ru> wrote in message 
·····························@g14g2000cwa.googlegroups.com...
> Good day,
>
> You are setting swank:*communication-style* too late.
> Use .swank.lisp in your home directory to customize swank behaviour.
>