Created attachment 375968 [details] ebuild for open-axiom-1.4.2 which crashes sbcl This error occurs on two complete different machines. Therefore a hardware problem is very unlikely. sbcl-1.1.16 and the new 1.1.17 crash when I try to open-axiom, see the attached ebuild. Thanks for looking into this: I get reproducably ; compiling (DEFUN |bfOR| ...)CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 0 (pc=0x100178c053, sp=0x7ffff6c8ec90) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8e5a0) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8dd10) The integrity of this image is possibly compromised. Continuing with fingers crossed. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8d5c0) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8ce70) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8c720) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8bfd0) The integrity of this image is possibly compromised. Continuing with fingers crossed. (no restarts: If you didn't do this on purpose, please report it as a bug.) debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8b880) The integrity of this image is possibly compromised. Continuing with fingers crossed. #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) debugger invoked on a SB-SYS:MEMORY-FAULT-ERROR in thread #<THREAD "main thread" RUNNING {1002F363E3}>: Unhandled memory fault at #x40200066. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. (no restarts: If you didn't do this on purpose, please report it as a bug.) Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded. Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {1002F363E3}> CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8b130) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8a9e0) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c8a290) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c89b40) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x100159ef30, sp=0x7ffff6c89380) The integrity of this image is possibly compromised. Continuing with fingers crossed. CORRUPTION WARNING in SBCL pid 5624(tid 140737353508608): Memory fault at 40200066 (pc=0x10007b9a4d, sp=0x7ffff6c88b78) The integrity of this image is possibly compromised. Continuing with fingers crossed. fatal error encountered in SBCL pid 5624(tid 140737353508608): Unhandled SIGILL. Welcome to LDB, a low-level debugger for the Lisp runtime environment.
Is this a new failure? What is the latest version of sbcl which compiles OpenAxiom successfully? Or what is the latest version of OpenAxiom which is compiled by sbcl successfully? sbcl compiles FriCAS without problems. Of course, now FriCAS and OpenAxiom are no longer as close to each other as they used to be. But still this fact suggests that something must be wrong in OpenAxiom, not in sbcl. (sbcl also compiles maxima fine.) I've informed the upstream. Let's wait for a reply.
Looks like the same problem as #376213. *** This bug has been marked as a duplicate of bug 376213 ***
