sbcl-help

Hi -
Total lisp newbie here trying to work thru Peter Siebel's excellent book
(just received it on Friday). I'm having problems getting sbcl to play
nicely with slime 1.2.1 on xemacs. I'm getting the following error
directly after I issue "M-x slime":
-------------------
; loading #P"/home/ksmith/software/slime-1.2.1/swank-loader.lisp"
; compiling file "/home/ksmith/software/slime-1.2.1/swank-backend.lisp"
(written 27 APR 2005 03:16:21 PM):
debugger invoked on a SB-KERNEL::MEMORY-FAULT-ERROR in thread 8660:
memory fault
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [ABORT] Exit debugger, returning to top level.
(SB-KERNEL::MEMORY-FAULT-ERROR)
0]
-------------------
I'm running the x86-64 sbcl 0.9.0 build on an otherwise problem-free
install of Ubuntu Hoary. I've installed/uninstalled sbcl and slime twice
to see if I possibly installed something incorrectly but with the same
results.
Thanks,
Kevin

On Sun, 2005-05-08 at 21:26 -0400, Kevin A. Smith wrote:
> I should also mention that sbcl starts fine from the command line. I'm
> not sure if the problem is with slime or sbcl. I'll be happy to take
> this to the right mailing list if someone could give me a hint.
Try it with a latest version of SLIME from CVS. Recent SBCL changes have
been breaking some things in SLIME (for the long term betterment). SLIME
has been tracking the canges but if you're using a down-rev SLIME, you
may be seeing those disconnects.
--
Dave Roberts <ldave@...>

Kevin A. Smith wrote:
> Dave Roberts wrote:
>
>> On Sun, 2005-05-08 at 21:26 -0400, Kevin A. Smith wrote:
>>
>>> I should also mention that sbcl starts fine from the command line.
>>> I'm not sure if the problem is with slime or sbcl. I'll be happy to
>>> take this to the right mailing list if someone could give me a hint.
>>
>>
>>
>> Try it with a latest version of SLIME from CVS. Recent SBCL changes have
>> been breaking some things in SLIME (for the long term betterment). SLIME
>> has been tracking the canges but if you're using a down-rev SLIME, you
>> may be seeing those disconnects.
>>
OK. Tried this with both FAIRLY-STABLE and HEAD. Still getting the same
error. Sounds like this may be more of a slime problem. Should I take my
questions over to slime-devel?
--Kevin

On Sun, 8 May 2005, Kevin A. Smith wrote:
> OK. Tried this with both FAIRLY-STABLE and HEAD. Still getting the same
> error. Sounds like this may be more of a slime problem. Should I take my
> questions over to slime-devel?
Have you verified that you're starting the SBCL you think you're starting
in Slime? What does the SBCL startup message (which should appear in
*inferior-lisp* say?
Also, to make the scenario a bit simpler you may want to enter the
directory where you have Slime, and start SBCL with
sbcl --load swank-loader.lisp --userinit /dev/null --sysinit /dev/null
Does that give the same results?
Cheers,
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."

"Kevin A. Smith" <kevin@...> writes:
> I'm running the x86-64 sbcl 0.9.0 build on an otherwise problem-free
> install of Ubuntu Hoary.
This is the problem. The kernel as distributed with Ubuntu Hoary
contains a bug which interferes with anything which uses userspace
traps. SBCL will start up in the console, but the first error, or the
first garbage-collection write barrier trap, will cause it to segfault.
The bug I reported is at
<https://bugzilla.ubuntu.com/show_bug.cgi?id=10246&gt;; it doesn't look
like it will be fixed, so you will have to build your own kernel, I'm
afraid. The patch linked from that bug works for me.
Cheers,
Christophe

Christophe Rhodes wrote:
> "Kevin A. Smith" <kevin@...> writes:
>
>
>>I'm running the x86-64 sbcl 0.9.0 build on an otherwise problem-free
>>install of Ubuntu Hoary.
>
>
> This is the problem. The kernel as distributed with Ubuntu Hoary
> contains a bug which interferes with anything which uses userspace
> traps. SBCL will start up in the console, but the first error, or the
> first garbage-collection write barrier trap, will cause it to segfault.
>
> The bug I reported is at
> <https://bugzilla.ubuntu.com/show_bug.cgi?id=10246&gt;; it doesn't look
> like it will be fixed, so you will have to build your own kernel, I'm
> afraid. The patch linked from that bug works for me.
>
> Cheers,
>
> Christophe
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Sbcl-help mailing list
> Sbcl-help@...
> https://lists.sourceforge.net/lists/listinfo/sbcl-help
>
Thanks for this info. Changing that one line in traps.c fixed it.
Thanks again,
Kevin