On Tue, May 13, 2014 at 4:32 AM, Helmut Jarausch <
jarau...@igpm.rwth-aachen.de> wrote:

> Hi,
>
> I'm trying to build open-axiom-1.4.2 with SBCL-1.1.18.
> It fails with strange memory errors like
>
> ; compiling (DEFUN |bfOR| ...)
> ; compiling (DEFUN |bfAND| ...)CORRUPTION WARNING in SBCL pid 9224(tid
> 140737353516800):
> Memory fault at 1878002f (pc=0x100099ca66, sp=0x7ffff6c8eaf8)
> The integrity of this image is possibly compromised.
> Continuing with fingers crossed.
> CORRUPTION WARNING in SBCL pid 9224(tid 140737353516800):
> Memory fault at 40200066 (pc=0x10015259aa, sp=0x7ffff6c8e430)
> The integrity of this image is possibly compromised.
> Continuing with fingers crossed.
> CORRUPTION WARNING in SBCL pid 9224(tid 140737353516800):
> Memory fault at 40200066 (pc=0x10015259aa, sp=0x7ffff6c8dbe0)
> The integrity of this image is possibly compromised.
> Continuing with fingers crossed.
>
> debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread
> #<THREAD "main thread" RUNNING {1002E5E1F3}>:
>   Unhandled memory fault at #x40200066.
>
> and so on.
>
> I have built Fricas and Maxima successfully with SBCL.
>
> What is so special about Open-Axiom?
>
> Of course, no source program should ever get a compiler in producing
> memory faults. But is it only SBCL which is wrong here?
>
> Is there a patch to build Open-Axiom with SBCL ?
>
> Many thanks for some hints,
> Helmut


Helmut,

Thanks for the report.  Issues related to OpenAxiom  should be reported to
OpenAxiom developers at

    open-axiom-de...@lists.sf.net
    open-axiom-b...@lists.sf.net

Are you by any chance building on Gentoo?  It looks the same as this issue:


https://groups.google.com/forum/#!msg/sbcl-help-archive/fTYViJjaotE/dsWMdRWPjJgJ

-- Gaby
_______________________________________________
Axiom-developer mailing list
Axiom-developer@nongnu.org
https://lists.nongnu.org/mailman/listinfo/axiom-developer

Reply via email to