Re: [Chicken-users] Chicken 4.8.0 tests segfault on OpenBSD 5.2 AMD64

[John Long]

On Wed, Dec 05, 2012 at 12:20:04PM -0500, Mario Domenech Goulart wrote:
> Hi John,
> 
> On Wed, 5 Dec 2012 17:23:09 +0000 John Long <address@hidden> wrote:
> 
> > Hi guys. This is weird because I had no problem building Chicken 4.8.0 on
> > OpenBSD MIPS recently. I am getting a segfault (core dumped) in the make
> > check. It seems to be dying pretty far along in the tests. It's 5,000 lines
> > of output. Do you want to see all of it? Here's a small snipped towards the
> > end:
> >
> > (PASS) (irregex-replace (quote not-an-irx) str)
> > (PASS) (irregex-replace foo foo (lambda (x) (quote not-a-string)))
> > (PASS) (irregex-replace/all (quote not-an-irx) str)
> > (PASS) (irregex-replace/all foo foo (lambda (x) (quote not-a-string)))
> >   1995 tests completed in 0.418 seconds
> >   1995 (100.00%) tests passed
> >   0 (0.00%) tests failed
> > ======================================== compiler/nursery stress test ...
> >   100000
> >   120000
> >   200000
> >   250000
> >   300000
> >   350000
> >   400000
> >   450000
> >   500000
> > ======================================== symbol-GC tests ...
> > ../chicken symbolgc-tests.scm -output-file a.c -verbose -include-path ..
> > gcc a.c -o a.o -c -fno-strict-aliasing -DHAVE_CHICKEN_CONFIG_H
> > -DC_ENABLE_PTABLES -O3 -fomit-frame-pointer
> > -I.. -I"/usr/local/include/chicken"
> > rm a.c
> > gcc a.o -o a.out -L.. -L"/usr/local/lib"  -Wl,-R"/usr/local/lib" -lchicken 
> > -lm -lpthread
> > ../libchicken.so: warning: strcpy() is almost always misused, please use 
> > strlcpy()
> > ../libchicken.so: warning: strcat() is almost always misused, please use 
> > strlcat()
> > ../libchicken.so: warning: sprintf() is often misused, please use snprintf()
> > rm a.o
> > Segmentation fault (core dumped) 
> > gmake[1]: *** [check] Error 139
> > gmake[1]: Leaving directory `/tmp/chicken-4.8.0'
> > gmake: *** [check] Error 2
> >
> > Any idea what could be wrong?
> 
> Do you always get that error?  The symbol-GC test is known to fail
> sometimes (see http://bugs.call-cc.org/ticket/724)

That looks pretty similar from 50,000 feet although it seems to me I also
got the "starting with 1232 symbols and interning 10000 symbols" messages a
few times but in the snippet I sent it appears to have died before that. I
can't remember whether I didn't redirect everything in what I sent above but
I can reproduce the failure so far 100% of the time (6 times in 6 tries). 

test environment is OpenBSD AMD64 5.2-stable, chicken 4.8.0

$ gcc -v
Reading specs from /usr/lib/gcc-lib/amd64-unknown-openbsd5.2/4.2.1/specs
Target: amd64-unknown-openbsd5.2
Configured with: OpenBSD/amd64 system compiler
Thread model: posix
gcc version 4.2.1 20070719 

Thank you.

/jl

-- 
ASCII ribbon campaign ( ) Powered by Lemote Fuloong
 against HTML e-mail   X  Loongson MIPS and OpenBSD
   and proprietary    / \    http://www.mutt.org
     attachments     /   \  Code Blue or Go Home!
 Encrypted email preferred  PGP Key 2048R/DA65BC04