[Openmcl-devel] Slime problem on windows
gb at clozure.com
Wed Oct 22 14:21:41 PDT 2008
On Wed, 22 Oct 2008, Marko KociÄ~G wrote:
> 2008/10/22 Gary Byers <gb at clozure.com>:
>> The procedure for getting a CCL distribution from the svn trunk is
>> described at:
>> The way that things are put together depends heavily on "svn:externals"
>> properties (these let distributions for different platforms share the
>> same sources and auxiliary files.) A real svn client understands
>> what these "properties" are; a web browser probably doesn't.
> That's it. Thanks. Slime now kinda work. I get the error message when
> starting slime, but after that it seems to work ok.
> Error is:
> Fault during read of memory address #xC4
> [Condition of type CCL::INVALID-MEMORY-ACCESS]
> 0: (CCL::XCMAIN 6225198)
> #:G122183 = 6225198
> #:G122193 = #<A Foreign Pointer [stack-allocated] #x17BF4B8>
> CCL::XP = #<A Foreign Pointer #x17BFA74>
> CCL::XCF = #<A Foreign Pointer #x18D0FD0>
> SIGNAL = 10
> CCL::CODE = 0
> CCL::ADDR = 196
> CCL::FRAME-PTR = 6505460
> 1: (CCL::%PASCAL-FUNCTIONS% 1 6225198)
> CCL::INDEX = 1
> CCL::ARGS-PTR-FIXNUM = 9633070
> CCL::LISP-FUNCTION = #<Compiled-function CCL::XCMAIN
> (Non-Global) #x8375B76>
> WITHOUT-INTERRUPTS = NIL
> CCL::*CALLBACK-TRACE-P* = #<error printing CCL::IMMEDIATE #x33>
What SLIME's backtrace is showing here is part of the process of calling
out to lisp after the lisp kernel has detected an exception (an invalid
memory access of some sort.) That isn't very interesting; the next
few older frames would (hopefully) show us something about what was
happening when the fault happened.
> I'll try to rebuild ccl to see if the error will persist, but it'll
> probably take some time for me to figure out how to do it.
? (rebuild-ccl :clean t)
will delete all FASL (.wx32fsl) files in the CCL hierarchy, compile
all sources into fasls, and rebuild the heap image.
On other platforms, other arguments to REBUILD-CCL will also cause
the lisp kernel (C and assembler code) to be rebuilt. Unfortunately,
Windows doesn't allow an executable file (wx86cl.exe) to be overwritten
while it's running, since that would be too useful.
More information about the Openmcl-devel