From: Bruce O'N. <ec...@pc...> - 2009-02-08 14:09:52
|
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. 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 |
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 |
From: Bruce O'N. <ec...@pc...> - 2009-02-09 16:07:07
|
Hi, Thanks for the quick response. I reverted the change to debug-int.lisp below > > 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. but I get the following on ppc. 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: room.test.sh test failed, expected 104 return code, got 1 I'll build sparc this evening. I use Debian lenny on an Ultra 2 and I find, in general, that sbcl builds and runs very well. With one small patch It also builds and runs well on a SparcStation 20 running NetBSD. Which system do you use which crashes so often? Thanks! cheers bruce |
From: Bruce O'N. <ec...@pc...> - 2009-02-09 19:33:44
|
Hi, Sorry, it seems that there is no change on sparc either. cheers bruce On Mon, Feb 09, 2009 at 05:06:57PM +0100, Bruce O'Neel wrote: > Hi, > > Thanks for the quick response. > > I reverted the change to debug-int.lisp below > > > > > 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. > > > but I get the following on ppc. > > > 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: room.test.sh > test failed, expected 104 return code, got 1 > > > I'll build sparc this evening. I use Debian lenny on an Ultra 2 and > I find, in general, that sbcl builds and runs very well. > > With one small patch It also builds and runs well on a SparcStation 20 > running NetBSD. > > Which system do you use which crashes so often? > > Thanks! > > cheers > > bruce > > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code to > build responsive, highly engaging applications that combine the power of local > resources and data with the reach of the web. Download the Adobe AIR SDK and > Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel |
From: Gábor M. <me...@re...> - 2009-02-09 20:50:46
|
On Lunes 09 Febrero 2009, Bruce O'Neel wrote: > Hi, > > Thanks for the quick response. > > I reverted the change to debug-int.lisp below > > > 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. Sorry, I was not nearly precise enough: simply reverting the chunk above would break the build as it refers to %caller-frame-and-pc. This is how the call to compute-calling-frame should look like: (compute-calling-frame (descriptor-sap (%caller-frame)) (%caller-pc) nil) Maybe you did this, already. I cannot see any other changes relevant to non-x86, but since the ppc is still down ... > but I get the following on ppc. > > > 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: room.test.sh > test failed, expected 104 return code, got 1 > > > I'll build sparc this evening. I use Debian lenny on an Ultra 2 and > I find, in general, that sbcl builds and runs very well. > > With one small patch It also builds and runs well on a SparcStation > 20 running NetBSD. > > Which system do you use which crashes so often? It's gcc31.fsffrance.org. Linux ada 2.6.24-1-sparc64-smp #1 SMP Mon Feb 11 15:06:50 UTC 2008 sparc64 GNU/Linux Debian/Lenny > Thanks! > > cheers > > bruce |
From: Bruce O'N. <ec...@pc...> - 2009-02-10 06:59:05
|
Hi, In terms of the Sparc64, we have a whole stack of spare V100s at work and for assorted other tasks I was planning on setting one up running lenny. I'm happy to give you an acccount. The diff I used was: --- debug-int.lisp 2009-02-05 10:56:46.000000000 +0100 +++ /home/edoneel/tmp/debug-int.lisp 2009-02-09 12:22:25.628363824 +0100 @@ -662,9 +662,12 @@ ;;; this function. (defun top-frame () (/noshow0 "entering TOP-FRAME") - (compute-calling-frame (descriptor-sap (%caller-frame)) - (descriptor-sap (%caller-pc)) - nil)) +; BEO + (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)) ;;; Flush all of the frames above FRAME, and renumber all the frames ;;; below FRAME. Anyway, I'll keep poking at it. Thanks! cheers bruce On Mon, Feb 09, 2009 at 09:50:32PM +0100, Gábor Melis wrote: > On Lunes 09 Febrero 2009, Bruce O'Neel wrote: > > Hi, > > > > Thanks for the quick response. > > > > I reverted the change to debug-int.lisp below > > > > > 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. > > Sorry, I was not nearly precise enough: simply reverting the chunk above > would break the build as it refers to %caller-frame-and-pc. This is how > the call to compute-calling-frame should look like: > > (compute-calling-frame (descriptor-sap (%caller-frame)) > (%caller-pc) > nil) > > Maybe you did this, already. I cannot see any other changes relevant to > non-x86, but since the ppc is still down ... > > > but I get the following on ppc. > > > > > > 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: room.test.sh > > test failed, expected 104 return code, got 1 > > > > > > I'll build sparc this evening. I use Debian lenny on an Ultra 2 and > > I find, in general, that sbcl builds and runs very well. > > > > With one small patch It also builds and runs well on a SparcStation > > 20 running NetBSD. > > > > Which system do you use which crashes so often? > > It's gcc31.fsffrance.org. > Linux ada 2.6.24-1-sparc64-smp #1 SMP Mon Feb 11 15:06:50 UTC 2008 > sparc64 GNU/Linux > Debian/Lenny > > > Thanks! > > > > cheers > > > > bruce > > |
From: Gábor M. <me...@re...> - 2009-02-10 08:39:47
|
On Martes 10 Febrero 2009, Bruce O'Neel wrote: > Hi, > > In terms of the Sparc64, we have a whole stack of spare V100s at work > and for assorted other tasks I was planning on setting one up running > lenny. I'm happy to give you an acccount. > > > The diff I used was: > > --- debug-int.lisp 2009-02-05 10:56:46.000000000 +0100 > +++ /home/edoneel/tmp/debug-int.lisp 2009-02-09 12:22:25.628363824 > +0100 @@ -662,9 +662,12 @@ > ;;; this function. > (defun top-frame () > (/noshow0 "entering TOP-FRAME") > - (compute-calling-frame (descriptor-sap (%caller-frame)) > - (descriptor-sap (%caller-pc)) > - nil)) > +; BEO > + (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)) > That's the thing: %caller-frame-and-pc does not exist anymore, TOP-FRAME should look exactly like this: (defun top-frame () (/noshow0 "entering TOP-FRAME") (compute-calling-frame (descriptor-sap (%caller-frame)) (%caller-pc) nil)) |