debugging guile test failure and segfault.

[Dan McMahill]

Hello,

I've managed to get guile-1.8.1 to build (with a few patches) on my 
NetBSD/alpha system.  Now I'm trying to investigate some failing tests. 
 The tests which fail are:

Running numbers.test
FAIL: numbers.test: max: big / real: (= big*5 (max big*5 -inf.0))
FAIL: numbers.test: max: real / big: (= big*5 (max -inf.0 big*5))
FAIL: numbers.test: min: big / real: (= big*5 (min big*5 +inf.0))
FAIL: numbers.test: min: real / big: (= big*5 (min +inf.0 big*5))

and then later:


Running r4rs.test
[1]   Segmentation fault      ${dir}${tst}
FAIL: check-guile

The others all pass which I guess is a good sign.

At this point, I have two questions.

1)  Is there a more or less simple way to step through the tests in an 
interactive mode where I can get to the failures in numbers.test to 
really see what values are involved and causing the failure?   I'm 
guessing that either I'm seeing an artifact of alphas being 64-bit 
systems or that alphas may deal differently with IEEE math and things 
like Inf and NaN.

2)  Is there a simple way to get the r4rs.test to run in the debugger so 
I can either track this down myself or provide some more useful feedback?

I'm also working on getting this going on Solaris-2.9/sparc but am not 
quite to the testsuite part.  I have a few bug fix patches there too. 
Once I get my various problems worked out, I'll submit a more cleaned up 
set of patches.

Thanks
-Dan