This is an automatically filed bug for a failed rebuild attempt for GCC 4.3. http://fedoraproject.org/wiki/JesseKeating/gcc43MassRebuildProposal Please verify why this build failed and fix it. http://koji.fedoraproject.org/koji/taskinfo?taskID=444164 Exit code was 1, check the build.log for the failed buildArch task.
scratch build 482744
; compiling (DEFINE-MOVE-VOP MOVE-FROM-DOUBLE ...)unhandled SB-SYS:MEMORY-FAULT-ERROR in thread #<SB-THREAD:THREAD "initial thread" {A714909}>: Unhandled memory fault at #x0. 0: (SB-DEBUG:BACKTRACE 128 #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {90B3F01}>) 1: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<SB-SYS:MEMORY-FAULT-ERROR {BEF46B1}> #<unavailable argument>) 2: (INVOKE-DEBUGGER #<SB-SYS:MEMORY-FAULT-ERROR {BEF46B1}>) 3: (INVOKE-DEBUGGER #<SB-SYS:MEMORY-FAULT-ERROR {BEF46B1}>) 4: (ERROR SB-SYS:MEMORY-FAULT-ERROR) 5: (SB-SYS:MEMORY-FAULT-ERROR) 6: (SB-SYS:MEMORY-FAULT-ERROR) 7: ("foreign function: #x805FD5C") 8: ("foreign function: #x805FFB8")
Confirmed on upstream sbcl ml, debian'ers are also seeing fatal problems on gcc-4.3-derived systems.
My most recent post to upstream ml: "[Sbcl-devel] sbcl doesn't run on gcc-4.3 environment?" http://sourceforge.net/mailarchive/forum.php?thread_name=fr3e81%242tj%241%40ger.gmane.org&forum_name=sbcl-devel
gcc43/kernel bug? sbcl devs pointed me to: "GCC 4.3.0 exposes a kernel bug" http://lwn.net/Articles/272048/ (I'm not currently an lwn subscriber, so can't access the article, yet).
See also possibly related cmucl issue, bug #434397
sbcl/f9 builds in fedora buildsys using RHEL5 continue to fail, http://koji.fedoraproject.org/koji/taskinfo?taskID=583155 I suspect they will continue to do so, until when/if the buildsys hosts' kernels are patched (see related bug #444178)
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
builds as of 2008-07-03, version 1.0.17-2.fc10.