unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: bug-guile@gnu.org
Subject: Re: crash and test failures with 1.8.1
Date: Fri, 17 Aug 2007 09:23:05 +1000	[thread overview]
Message-ID: <87d4xngj3a.fsf@zip.com.au> (raw)
In-Reply-To: <4665619A.5000304@mtl.mit.edu> (Dan McMahill's message of "Tue, 05 Jun 2007 09:14:02 -0400")

[belated followup]

Dan McMahill <mcmahill@mtl.mit.edu> 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 "$@"



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


      reply	other threads:[~2007-08-16 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 13:14 crash and test failures with 1.8.1 Dan McMahill
2007-08-16 23:23 ` Kevin Ryde [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d4xngj3a.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=bug-guile@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).