[Openmcl-devel] Problems with openMCL slime and Aquamacs (Mac OS X)

Philippe Sismondi psismondi at arqux.com
Sat Oct 24 15:50:43 UTC 2009


Ok, I got around to putting (setf swank:*communication-style* nil) in  
my swank startup file

I have started slime a dozen times or so with this setting (and  
checked that the value was indeed nil). So far it has not failed. Who  
knows whether it will crash the 20th time. I shall run like this for a  
while and see what happens.

I almost hope this is not the problem. If there is some kind of race/ 
threading problem I expect it will be hell to track down, and I am  
certainly not the person to do it.

Ah well, such is life.

- Phil -



On 2009-10-24, at 3:31 AM, Tobias C. Rittweiler wrote:

> Philippe Sismondi <psismondi at arqux.com> writes:
>
>> I should emphasize that the problem is intermittent, from which I
>> infer that any of ccl, slime, and asdf or some combination may still
>> be the culprit(s). What I mean is, for example, loading asdf in raw
>> ccl (without emacs+slime) does not prove that it's not asdf, since
>> sometimes asdf loads fine when using emacs+slime+ccl. And so  
>> forth....
>
> Given that it's non-deterministic, there's the possibility that the
> cache clobbering Gary talked about may be due to multiple accesses  
> from
> threads.
>
> Could you try putting (setf swank:*communication-style* nil) into your
> ~/.swank.lisp (which makes Slime not use threads), and see if you can
> reproduce the problem?
>
>  -T.
>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel




More information about the Openmcl-devel mailing list