From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 10336-done@debbugs.gnu.org
Subject: bug#10336: lexical vars are collectable test is failing
Date: Thu, 02 Feb 2012 00:16:04 +0100 [thread overview]
Message-ID: <87pqdyp2kr.fsf@pobox.com> (raw)
In-Reply-To: <87mx99f0wz.fsf_-_@pobox.com> (Andy Wingo's message of "Fri, 27 Jan 2012 19:36:12 +0100")
On Fri 27 Jan 2012 19:36, Andy Wingo <wingo@pobox.com> writes:
> On Wed 25 Jan 2012 17:10, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Second thing, it suffices to insert a function call like
>> ((lambda (x) #f) #f) just before calls to ‘gc’ to solve the problem.
>>
>> So I’m thinking we may have a real bug here.
>
> I pushed an experimental patch that attempts to NULL out variables that
> are local to the VM. Let's see what hydra does with it.
In the end that failed. I pushed a different patch that tried to NULL
out recursively called C stack frames. Perhaps it worked? As tests are
passing, I will close this one for now. It's possible that simply
recursing through the VM wouldn't work well, as there might be stack
slots in vm_engine that don't get set in all code paths. If we see
errors in the future, let's just mark those as flaky and move on. Let's
also try to reduce the number of UNRESOLVED results in general, so that
these hacks will be more visible.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2012-02-01 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111220210919.0YNV7.4169.root@cdptpa-web14-z02>
2011-12-21 0:59 ` Holidays vs. release dsmich
2012-01-04 23:57 ` bug#10336: " Ludovic Courtès
2012-01-25 16:10 ` Ludovic Courtès
2012-01-25 18:07 ` Andy Wingo
2012-01-26 4:40 ` dsmich
2012-01-25 20:34 ` Ludovic Courtès
2012-01-25 23:05 ` Andy Wingo
2012-01-27 18:36 ` bug#10336: lexical vars are collectable test is failing Andy Wingo
2012-02-01 23:16 ` Andy Wingo [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=87pqdyp2kr.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10336-done@debbugs.gnu.org \
--cc=ludo@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).