[Openmcl-devel] CLX crash - FIXED!! and mcclim now works!!!!

[Henry Irvine]

Gary, I believe that you must have really hit the caffeine!
With the latest cvs checkout, clx now compiles and works.  I also tried
loading the latest release of mcclim.  That works too. Very Cool.

With regards to why my ppc version of openmcl was having no troubles  
with
clx, well, I think that it is still an early 1.0 version with no  
updates.

Thanks,
Henry Irvine

On Jan 16, 2007, at 4:25 AM, Gary Byers wrote:

>
> Fascinating as that may (or may not ...) be, the problem exposed in
> the CLX case included some confusion over whether the socket used
> to communicate with the X server was a binary stream.  Using  
> CCL:STREAM-READ-IVECTOR to read from the socket into a a vector
> of (UNSIGNED-BYTE 8)s wound up calling a method that treated
> the target vector as if it were a string (and expanded each octet
> from the stream into a 32-bit character, filling the buffer with
> garbage and stepping on anything near it in memory, leading to
> the kinds of symptoms that you reported.)
>
> I think that this is straightend out in CVS now.
>
> On Mon, 15 Jan 2007, Gary Byers wrote:
>
>> My first guess is that something that used to work when characters
>> were 8 bits wide and strings were vectors of 8-bit char-codes is
>> failing in a world where characters are basically 32 bits wide;
>>
>> On Mon, 15 Jan 2007, Henry Irvine wrote:
>>
>>> Just a guess, but since this all seems to work on the ppc port of
>>> open mcl, I believe that what follows is a problem with openmcl
>>> rather than clx...
>>>
>>> System details:
>>> openmcl with cvs updates current to 14 Jan,
>>> clx -- fresh download off of clozure, same error happens with a
>>> current checkout of the telent source.
>>> mac-pro with os version 10.4.8
>>>
>>> details from debugger output are in the following paste...
>>>
>>> http://paste.lisp.org/display/35398
>>>
>>> I am not sure how to narrow down what is actually breaking though.
>>>
>>> Henry Irvine