unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Petr Gajdos <pgajdos@suse.cz>
To: Andy Wingo <wingo@pobox.com>
Cc: 10096@debbugs.gnu.org
Subject: bug#10096: Failing gc.test for i586
Date: Thu, 24 Nov 2011 08:41:41 +0100	[thread overview]
Message-ID: <20111124074141.GA31854@laura.suse.cz> (raw)
In-Reply-To: <87d3cjniv6.fsf@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

On Wed, Nov 23, 2011 at 01:06:21PM +0100, Andy Wingo wrote:
> On Mon 21 Nov 2011 15:46, Petr Gajdos <pgajdos@suse.cz> writes:
> 
> > gc.test is failing with guile 2.0.3 for me on i586:
> > FAIL: gc.test: gc: Unused modules are removed
> >
> > I don't observe this for guile 2.0.2. Could you please 
> > guide me to resolve this issue?
> 
> Hummmm.  Well, on the one side, it is not really a fatal failure.  This
> tests allocates 1000 modules, then does a few gc runs, then checks to
> make sure they were all collected.  Since libgc is a conservative
> collector, it is possible that it mistakenly thinks one of those modules
> is still alive -- a problem that is more acute on 32-bit systems.  It is
> also dependent on the compiler you use, the version of libgc, etc.
> 
> I think if I were you, I would just ignore this error.  I know it's not
> a very good answer, but does that work for you?

Andy, 

thanks a lot for you answer, I will ignore it.

Best regards,
Petr

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-11-24  7:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 14:46 bug#10096: Failing gc.test for i586 Petr Gajdos
2011-11-21 15:13 ` Petr Gajdos
2011-11-23 12:06 ` Andy Wingo
2011-11-24  7:41   ` Petr Gajdos [this message]
2011-12-03  0:26   ` Andreas Schwab
2012-01-31 21:36     ` Andy Wingo
2012-02-01 15:16       ` Andreas Schwab
2012-02-01 15:54         ` Andy Wingo
2012-02-01 16:13           ` Andreas Schwab
2012-02-01 23:11             ` Andy Wingo

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=20111124074141.GA31854@laura.suse.cz \
    --to=pgajdos@suse.cz \
    --cc=10096@debbugs.gnu.org \
    --cc=wingo@pobox.com \
    /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).