From: Gábor M. <me...@re...> - 2009-02-08 16:14:12
|
On Domingo 08 Febrero 2009, Bruce O'Neel wrote: > Hi, > > The changes in 1.0.25.9 cause some problems in both ppc and sparc. > > For sparc the errors look like: > > ; registering #<SYSTEM SB-BSD-SOCKETS {30A4B429}> as SB-BSD-SOCKETS > ; registering #<SYSTEM SB-BSD-SOCKETS-TESTS {30BCF611}> as > SB-BSD-SOCKETS-TESTS (SYS:CONTRIB;SB-POSIX;CONSTANTS.LISP.NEWEST > SYS:CONTRIB;SB-POSIX;CONSTANTS.FASL.NEWEST > /home/edoneel/tmp/sbcl-1.0.25.9/contrib/sb-posix/constants.fasl > /home/edoneel/tmp/sbcl-1.0.25.9/contrib/sb-posix/foo.c > /home/edoneel/tmp/sbcl-1.0.25.9/contrib/sb-posix/a.out > > /home/edoneel/tmp/sbcl-1.0.25.9/contrib/sb-posix/constants.lisp-temp) > unhandled SIMPLE-ERROR: segmentation violation at #X1C438 > > Argh! error within --disable-debugger error handling > make: *** [all] Error 1 > make: Leaving directory > `/home/edoneel/tmp/sbcl-1.0.25.9/contrib/sb-simple-streams' make: > Entering directory `/home/edoneel/tmp/sbcl-1.0.25.9/contrib/sb-sprof' > > and ends with: > > WARNING! Some of the contrib modules did not build successfully or > pass their self-tests. Failed contribs:" > asdf-install > sb-bsd-sockets > sb-posix > sb-simple-streams > > sh run-tests.sh stops almost right away. > > > PPC seems to build ok all the way through, but, the test output is > different. > > >From 1.0.25.9 we get: > > Finished running tests. > Status: > Expected failure: float.pure.lisp / (SCALE-FLOAT-OVERFLOW > BUG-372) Expected failure: float.pure.lisp / (ADDITION-OVERFLOW > BUG-372) Invalid exit status: debug.impure.lisp > Invalid exit status: dynamic-extent.impure.lisp > Expected failure: external-format.impure.lisp / > (CHARACTER-DECODE-LARGE FORCE-END-OF-FILE) Expected failure: > packages.impure.lisp / USE-PACKAGE-CONFLICT-SET Expected failure: > packages.impure.lisp / IMPORT-SINGLE-CONFLICT Failure: > step.impure.lisp / STEP-INTO > Failure: step.impure.lisp / STEP-NEXT > Failure: step.impure.lisp / STEP-OUT > Failure: step.impure.lisp / STEP-START-FROM-BREAK > Failure: step.impure.lisp / STEP-FRAME > Failure: step.impure.lisp / STEP-BACKTRACE > Failure: step.impure.lisp / STEP-NEXT/2 > Failure: step.impure.lisp / STEP-OUT/2 > Invalid exit status: unwind-to-frame-and-call.impure.lisp > Invalid exit status: foreign.test.sh > Invalid exit status: room.test.sh > test failed, expected 104 return code, got 1 > > > 'Normally' the results look like the run from 1.0.25.8: > > Finished running tests. > Status: > Expected failure: float.pure.lisp / (SCALE-FLOAT-OVERFLOW > BUG-372) Expected failure: float.pure.lisp / (ADDITION-OVERFLOW > BUG-372) Expected failure: debug.impure.lisp / (UNDEFINED-FUNCTION > BUG-346) Failure: debug.impure.lisp / (UNDEFINED-FUNCTION > BUG-353) Expected failure: debug.impure.lisp / (TRACE ENCAPSULATE > NIL) Expected failure: debug.impure.lisp / (TRACE-RECURSIVE > ENCAPSULATE NIL) Unhandled error dynamic-extent.impure.lisp > Expected failure: external-format.impure.lisp / > (CHARACTER-DECODE-LARGE FORCE-END-OF-FILE) Expected failure: > packages.impure.lisp / USE-PACKAGE-CONFLICT-SET Expected failure: > packages.impure.lisp / IMPORT-SINGLE-CONFLICT Invalid exit status: > foreign.test.sh > Invalid exit status: room.test.sh > test failed, expected 104 return code, got 1 > > > Thanks for any hints as to what can be fixed. I will poke at this > over the next few days. Sorry, that would probably be caused by this change: --- a/src/code/debug-int.lisp +++ b/src/code/debug-int.lisp @@ -662,8 +662,9 @@ ;;; this function. (defun top-frame () (/noshow0 "entering TOP-FRAME") - (multiple-value-bind (fp pc) (%caller-frame-and-pc) - (compute-calling-frame (descriptor-sap fp) pc nil))) + (compute-calling-frame (descriptor-sap (%caller-frame)) + (descriptor-sap (%caller-pc)) + nil)) Simply reverting this part should fix it. The ppc machine I usually access is down, so please test it. As to the sparc, that has been my recent experience building versions ranging from 1.0.24.40 to 1.0.25.8: it bombs undeterministically on Sparc64. > BTW, the sbcl buildbot has been down for a while. I'll probably set > up buildbot for a work project, and, might be able to setup a new > sbcl one if there is interest. > > Thanks. > > cheers > > bruce |