guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: debugging guile test failure and segfault.


From: Ludovic Courtès
Subject: Re: debugging guile test failure and segfault.
Date: Wed, 06 Jun 2007 10:24:30 +0200
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)

Hi,

Dan McMahill <address@hidden> writes:

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

These tests should be using `eqv?' rather than `='.  This was fixed on
2006-12-02 (and will appear in the next release).  So, that's nothing to
worry about.

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

I guess you'll have to send us a stack trace.  :-)  So you need to make
sure you compile Guile with the `-g' flags (e.g., by running "make
CFLAGS=-g"); then you can run "gdb libguile/.libs/lt-guile core",
assuming a `core' file was generated when it segfaulted.

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

>From the top-level build directory, you can run:

  $ ./pre-inst-guile test-suite/tests/numbers.test

But for `r4rs.test', you'll need something more complicated:

  $ ./pre-inst-guile -c "
     (module-set! (resolve-module '(test-suite guile-test))
                  'test-suite \"$PWD/test-suite/tests\")
     (module-set! (resolve-module '(test-suite guile-test))
                  'tmp-dir \"/tmp\")
     (load \"test-suite/tests/r4rs.test\")"

(This could surely be improved...)

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

See above: run the debugger on the `core' file.

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

Nice!

Thanks,
Ludovic.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]