[Openmcl-devel] CVS breaks slime?

[Gary Byers]

I couldn't reproduce this; SLIME seemed to run fine with the latest
OpenMCL under LinuxPPC.  (I had a SLIME from 05-08-12 and also tried
the latest SLIME from CVS.)

; SLIME 2005-08-29
CL-USER> (lisp-implementation-version)
"Version 1.0-pre-050828b (LinuxPPC32)"

While all of the hysteria is going on, can you see anything interesting
in the *inferior-lisp* buffer ?

On Mon, 29 Aug 2005, Derrick Baumer wrote:

> I just downloaded the latest CVS bleeding-edge OpenMCL and got it to
> work (which made me quite proud, no, really), and ran the program I've
> been working on with a huge smile on my face.  Assuming recompiles would
> be necessary, I deleted my ~/.slime directory and loaded emacs to get to
> work.  Typing M-x slime got me this:
>
>
>
> ; loading system definition from /usr/share/common-lisp/systems/asdf-install.asd into #<Package "ASDF0">
> ; registering #<SYSTEM ASDF-INSTALL #x353E1A0E> as ASDF-INSTALL
> Welcome to OpenMCL Version 1.0-pre-050828b (LinuxPPC32)!
> ? ;Loading #P"/usr/local/slime-cvs/swank-loader.lisp"...
> ;Compiling "/home/system/local/slime-cvs/swank-backend.lisp"...
> ;Loading #P"/home/derrick/.slime/fasl/openmcl-1.0-unix-powerpc/swank-backend.pfsl"...
> ;Compiling "/home/system/local/slime-cvs/nregex.lisp"...
> ;Loading #P"/home/derrick/.slime/fasl/openmcl-1.0-unix-powerpc/nregex.pfsl"...
> ;Compiling "/home/system/local/slime-cvs/metering.lisp"...
> ;Loading #P"/home/derrick/.slime/fasl/openmcl-1.0-unix-powerpc/metering.pfsl"...
> ;Compiling "/home/system/local/slime-cvs/swank-openmcl.lisp"...
> ;Compiler warnings for "/home/system/local/slime-cvs/swank-openmcl.lisp" :
> ;   Unused lexical variable STREAM, in (MAKE-STREAM-INTERACTIVE (T)).
> ;Loading #P"/home/derrick/.slime/fasl/openmcl-1.0-unix-powerpc/swank-openmcl.pfsl"...
> ;Compiling "/home/system/local/slime-cvs/swank-gray.lisp"...
> ;Loading #P"/home/derrick/.slime/fasl/openmcl-1.0-unix-powerpc/swank-gray.pfsl"...
> ;Compiling "/home/system/local/slime-cvs/swank.lisp"...
> ;Compiler warnings for "/home/system/local/slime-cvs/swank.lisp" :
> ;   Unused lexical variable THREAD, in SEND-TO-SOCKET-IO.
> ;Loading #P"/home/derrick/.slime/fasl/openmcl-1.0-unix-powerpc/swank.pfsl"...
> ; Warning: These Swank interfaces are unimplemented:
> ;           (ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER CALLS-WHO MACROEXPAND-ALL REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN TOGGLE-TRACE)
> ; While executing: SWANK-BACKEND::WARN-UNIMPLEMENTED-INTERFACES
> ;Compiler warnings for "/home/system/local/slime-cvs/swank.lisp" :
> ;   Undefined function SWANK-MOP:FINALIZE-INHERITANCE, in (SWANK::EXTRA-KEYWORDS ((EQL 'MAKE-INSTANCE))).
> ;   Undefined function SWANK-MOP:COMPUTE-APPLICABLE-METHODS-USING-CLASSES, in SWANK::APPLICABLE-METHODS-KEYWORDS.
> ;Compiler warnings for "/home/system/local/slime-cvs/swank-openmcl.lisp" :
> ;   Undefined function #:EQL-SPECIALIZER-OBJECT, in SWANK-BACKEND::SPECIALIZER-NAME.
> ;   Undefined function #:CLASS-NAME, in SWANK-BACKEND::SPECIALIZER-NAME.
> #P"/home/system/local/slime-cvs/swank-loader.lisp"
> ? ;; Swank started at port: 34757.
> 34757
> ?
>> Error in process control-thread(3): No applicable method for args:
>>                                      (NIL)
>>                                      to #<STANDARD-GENERIC-FUNCTION PROCESS-KILL #x350DB08E>
>> While executing: #<CCL::STANDARD-KERNEL-METHOD NO-APPLICABLE-METHOD (T)>
>
>
> ;;;
> ;;; #<PROCESS control-thread(3) [Active] #x3552DD76> requires access to Shared Terminal Input
> ;;;
>
>> Error in process control-thread(3): Failed assertion: (EQ CCL::CURRENT (CCL::SHARED-RESOURCE-CURRENT-OWNER CCL::RESOURCE))
>> While executing: CCL::%ASSERTION-FAILURE
> -snip-
>
>
>
> The last set, from ;;; #<PROCESS control-thread(3)... repeats
> ad-infinitum, scrolling as fast as emacs will keep up, which is,
> fortunately, not so fast on my old system.
>
> This happens with the relase (1.2.1) version of slime and the latest
> slime from CVS (the cut-n-paste above is from the CVS version of slime -
> I can get you the release-version output as you like).
>
> It's hard for me to tell if this is an OpenMCL bug or a Slime bug,
> except that the 0.14.3 OpenMCL worked (for my purposes) beautifully with
> slime 1.2.1 and/or the CVS release.  I'd enjoy the opportunity to help
> debug this if you can give me (very thorough) pointers on where/how I
> should look.
>
> Thank you,
> Derrick Baumer
>
> (PS. Ubuntu Linux 5.4 (Hoary), currently up to date, on a 333 Mhz iMac
> w/ 160Mb RAM, tangerine...)
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>
>