unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Dan McMahill <mcmahill@mtl.mit.edu>
To: bug-guile@gnu.org
Subject: crash and test failures with 1.8.1
Date: Tue, 05 Jun 2007 09:14:02 -0400	[thread overview]
Message-ID: <4665619A.5000304@mtl.mit.edu> (raw)

Hello,

I posted most of this to guile-user but realized it is more of a 
bug/developer issue...

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 first failing test is:

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

There is one other which will cause a segfault and then some others 
which run but do not pass the test.

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.  FWIW, a friend tried this on a linux x86_64 system 
and also saw the numbers.test failure.

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 have a handful of patches to get guile-1.8.1 to build on 
solaris-2.9/sparc as well and I'm failing some tests there too.  I'll 
try to clean up the patches I have and get them sent in.

Thanks
-Dan


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


             reply	other threads:[~2007-06-05 13:14 UTC|newest]

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

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=4665619A.5000304@mtl.mit.edu \
    --to=mcmahill@mtl.mit.edu \
    --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).