Re: crash and test failures with 1.8.1

[Kevin Ryde]

[belated followup]

Dan McMahill <address@hidden> writes:
>
> Running numbers.test
> FAIL: numbers.test: max: big / real: (= big*5 (max big*5 -inf.0))

Thanks, that was a bug in the test (I believe the code is/was ok).

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

Don't know anything about that.

> 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?

Not really, but the tests are supposed to be relatively straightforward
so you can pick out the values and try them.

> 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?

Slightly painful.  The last time I had to do that I changed the last
line of the generated pre-inst-guile script from

        exec $GUILE "$@"
to
        exec /my/build/dir/libtool gdb --args $GUILE "$@"