Hi,
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)) (slime-setup)
...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 1.0.33.6.
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.
Regards, Andy Chambers
Andy Chambers achambers.home@googlemail.com writes:
Hi,
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)) (slime-setup)
...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 1.0.33.6.
SBCL is now at the 1.0.37 version