On Tue, Aug 16, 2011 at 11:53:05AM -0400, Jim Wise wrote:
> Jim Wise <jwise@...> writes:
> > Juho Snellman <jsnell@...> writes:
> >> Barring any surprises, I'll release SBCL 1.0.51 next weekend. Please
> >> let sbcl-devel know of any regressions, and try not to add any new
> >> ones in the meanwhile :-)
> > Solaris/x86_64 and Solaris x86 look good for the release in the default
> > build. I'll test Darwin, and experimental threading support later.
> > Thanks,
> In further testing, I am seeing a new broken test on SunOS/x86:
> Finished running tests.
> Skipped (broken): debug.impure.lisp / (TRACE ENCAPSULATE NIL)
> Skipped (broken): debug.impure.lisp / (TRACE-RECURSIVE ENCAPSULATE
> Expected failure: packages.impure.lisp / USE-PACKAGE-CONFLICT-SET
> Expected failure: packages.impure.lisp / IMPORT-SINGLE-CONFLICT
> Invalid exit status: room.test.sh
> (40 tests skipped for this combination of platform and features)
> test failed, expected 104 return code, got 1
> I've enclosed the output of a manual run of room.test.sh.
> This problem does not occur on SunOS/x86_64.
I just recently fixed the mail system on my OpenBSD/x86 machine and
realized that the same problem has existed there since ~Aug 1. An
automated bisection shows the problematic commit as:
Author: Nikodemus Siivola <nikodemus@...>
Date: Mon Aug 1 16:46:26 2011 +0300
more robust backtraces for syscalls on x86
* new optimization policy: ALIEN-FUNCALL-SAVES-FP-AND-PC Set to 3 for
self-build on x86 to get reliable more backtraces there, and 0 for
other platforms. (1 matches the old SPEED <= DEBUG behaviour.)
* When using a saved FP, and an interrupt context has a bogus
FP, assume it is an interrupted syscall frame.
If I update to the current HEAD and unconditionally set
sb!c:alien-funcall-saves-fp-and-pc to 0 in make-host-2.lisp then the
room test is able to finish normally, with normal-looking output:
Dynamic space usage is: 38,983,360 bytes.
Read-only space usage is: 2,760 bytes.
Static space usage is: 1,712 bytes.
Control stack usage is: 1,656 bytes.
Binding stack usage is: 392 bytes.
Garbage collection is currently enabled.
Breakdown for dynamic space:
9,188,968 bytes for 12,169 code objects.
9,164,056 bytes for 1,145,507 sap objects.
5,068,968 bytes for 633,621 cons objects.
3,878,848 bytes for 89,773 instance objects.
3,451,920 bytes for 58,112 simple-vector objects.
2,981,984 bytes for 320,312 bignum objects.
5,625,240 bytes for 132,569 other objects.
39,359,984 bytes for 2,392,063 dynamic objects (space total.)
test room test ok