Development of Steel Bank Common Lisp

Juho Snellman | 2 Oct 2007 13:25

Fwd: SBCL hash test failure

Forwarding a message from a non-subscriber to sbcl-devel.

IIRC this test failure has been intermittently seen by others every
now and then, and it's passing on the buildbot ppc right now, so I'm
guessing that my changes aren't to blame. But it seems really strange
that the error (weak hash-table hanging on to a single key that it
shouldn't be retaining) would happen on ppc, where the gc should be
precise. Does anyone have any bright ideas on what's happening?

From: Robert Brown <brown <at> google.com>
Subject: SBCL hash test failure
Date: 2007-10-02 01:56:52 GMT


I'm sorry for mailing this to you directly.  I should send it to the SBCL
developer mailing list, but I'd probably have to join the mailing list first
in order to report a bug.  Also, I know you've been working on the hash
table code recently, so the test failure I noticed may be related to your
recent changes.

Anyway, I built the latest SBCL today and noticed that one of the weak hash
table tests fails on my PowerPC Macintosh -- output below.

(Continue reading)

headers

Harald Hanche-Olsen | 13 Oct 2007 14:52

Re: Fwd: SBCL hash test failure

+ Juho Snellman <jsnell <at> iki.fi>:

> Forwarding a message from a non-subscriber to sbcl-devel.
> 
> IIRC this test failure has been intermittently seen by others every
> now and then, and it's passing on the buildbot ppc right now, so I'm
> guessing that my changes aren't to blame. [...]
> Does anyone have any bright ideas on what's happening?

I certainly don't, but I notice that you didn't get a backtrace with
the error report.  Here, you can have mine.  I don't know if it is
useful or not.

- Harald

Made with 1.0.10.45 on macosx/ppc (built using 1.0.10.13):
0: (SB-DEBUG::DEBUG-LOOP-FUN)
1: (SB-DEBUG::DEBUG-LOOP-FUN)
2: (INTERNAL-DEBUG)
3: (SB-DEBUG::%INVOKE-DEBUGGER #<SIMPLE-ERROR {118A7A49}>)
4: ((LAMBDA ()))
5: (SB-IMPL::CALL-WITH-SANE-IO-SYNTAX #<CLOSURE (LAMBDA #) {118A7DE5}>)
6: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA #) {118A7DC5}>)
7: (INVOKE-DEBUGGER #<SIMPLE-ERROR {118A7A49}>)
8: (INVOKE-DEBUGGER #<SIMPLE-ERROR {118A7A49}>)
9: (REALLY-INVOKE-DEBUGGER #<SIMPLE-ERROR {118A7A49}>)
10: ((LAMBDA (ERROR)) #<SIMPLE-ERROR {118A7A49}>)
11: ((LAMBDA (ERROR)) #<SIMPLE-ERROR {118A7A49}>)
12: (SIGNAL #<SIMPLE-ERROR {118A7A49}>)
13: (ERROR #<SIMPLE-ERROR {118A7A49}>)

(Continue reading)