Re: [Sbcl-help] Gentoo bug 508990

[Orivej D. <or...@gm...>]

> > 1. I can reproduce the problem. It stems from SBCL being run effectively
> > as "sbcl --eval ... < /dev/null". When SBCL enters debugger due to an
> > error in the build process, it reads EOF, exits with code 0, and the
> > build continues with this happening many times until finally SBCL
> > encounters memory fault.

> Thanks for the detective work.  I missed your message earlier.

My message "has been automatically rejected" from open-axiom-devel.

Anyway, its second point (on the first actual error), and conclusion in
the third were mistaken.

> > 3. I'm going to investigate the cause of memory fault, but it should not
> > concern OpenAxiom or Gentoo.

So far I found that although corruption happens when

     ../../src/driver/open-axiom --execpath=../lisp/lisp --output=strap/ast.fasl --compile --load-directory=strap /var/tmp/portage/sci-mathematics/open-axiom-1.4.2/work/open-axiom-1.4.2/src/boot/strap/ast.clisp

executes

     ../lisp/lisp --noinform --end-runtime-options --noprint --no-sysinit --no-userinit --end-toplevel-options -- --output=strap/ast.fasl --compile --load-directory=strap /var/tmp/portage/sci-mathematics/open-axiom-1.4.2/work/open-axiom-1.4.2/src/boot/strap/ast.clisp

in BUILDDIR/src/boot in the sandbox, the latter command by itself completes compilation with no error.