[slime-devel] Memory corruption error triggered by slime on sbcl

Andy Chambers achambers.home at googlemail.com
Mon Apr 5 14:51:06 UTC 2010


slime seems to trigger a memory corruption error for me on sbcl when I
have the following
declaration at the bottom of my .sbclrc

(declaim (optimize (safety 3) (debug 3) (speed 0) (space 0)))

Here's the relevant part from my .emacs

(require 'slime)

(setq inferior-list-program "~/bin/lisp"
     slime-net-coding-system 'utf-8-unix)

;; (slime-setup '(slime-repl slime-c-p-c slime-fancy
;;                        slime-fancy-inspector))

...and I've just pulled the latest source from nablaone's git mirror
so I believe this is
a problem with the current source.

The version of sbcl I'm running is

The error is triggered when entering the debugger, but only when doing
so through slime.
Also, the address provided in the message below is always the same.
I'll carry on digging
but I'm hoping the details here make it obvious to someone smarter than myself.

* CORRUPTION WARNING in SBCL pid 4108(tid 3048868752):
Memory fault at 720550f8 (pc=0x901b52a, sp=0xb5b9ece0)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.

Andy Chambers

More information about the slime-devel mailing list