emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#10336: closed (Holidays vs. release)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#10336: closed (Holidays vs. release)
Date: Wed, 01 Feb 2012 23:17:02 +0000

Your message dated Thu, 02 Feb 2012 00:16:04 +0100
with message-id <address@hidden>
and subject line Re: bug#10336: lexical vars are collectable test is failing
has caused the debbugs.gnu.org bug report #10336,
regarding Holidays vs. release
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
10336: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10336
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Re: Holidays vs. release Date: Tue, 20 Dec 2011 19:59:34 -0500
---- address@hidden wrote: 
> 
> ---- "Ludovic Courtès" <address@hidden> wrote: 
> > Hello Guilers!
> > 
> > I initially thought it would be great to push a 2.0.4 tarball by the end
> > of the year, but since I’ll be on holidays starting from tomorrow until
> > Jan. 3rd, I won’t be able to make it.  Sorry about that!
> 
> I'm still getting that one failure in make check.  Something about gc a 
> lexicals?  (Sorry I'm not at that machine.)  Probably would be a good idea to 
> tune that up before release anyway.
> 
> I'll post details when I can.

I'm on a 32bit Debian intel system.  libgc is 7.2alpha4

git describe is
v2.0.3-82-ga2c6601

The single failure running make check is

Running gc.test
FAIL: gc.test: gc: Lexical vars are collectable


-Dale




--- End Message ---
--- Begin Message --- Subject: Re: bug#10336: lexical vars are collectable test is failing Date: Thu, 02 Feb 2012 00:16:04 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
On Fri 27 Jan 2012 19:36, Andy Wingo <address@hidden> writes:

> On Wed 25 Jan 2012 17:10, address@hidden (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/


--- End Message ---

reply via email to

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