chicken-users
[Top][All Lists]
Advanced

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

Re: [Chicken-users] Build Failure (maybe infinite recursion) on x86_64 L


From: Taylor Venable
Subject: Re: [Chicken-users] Build Failure (maybe infinite recursion) on x86_64 Linux
Date: Fri, 6 Mar 2009 09:11:05 -0500
User-agent: Mutt/1.5.18 (2008-05-17)

On Fri, Mar 06, 2009 at 01:45:10PM +0100, felix winkelmann wrote:
> On Wed, Mar 4, 2009 at 4:32 PM, Taylor Venable <address@hidden> wrote:
> > Hi all,
> >
> > When building Chicken 3.4.7 and higher (up to 3.5.2) on Ubuntu 8.10
> > x86_64 the chicken compiler goes into an infinite recursion. ?CPU
> > usage spikes, memory usage increases boundlessly, and no output is
> > ever produced. ?In Chicken 3.4.7 the file that when compiled triggers
> > this behaviour is utils.scm and for a build process I am using:
> >
> > ? ?make PLATFORM=linux bootstrap
> > ? ?make PLATFORM=linux CHICKEN=./chicken-boot
> >
> > The command that causes the infinite recursion is:
> >
> > ? ?./chicken-boot utils.scm -quiet -no-trace -optimize-level 2
> > -include-path . -include-path ./ -explicit-use -output-file utils.c
> >
> > If any other information would be helpful to diagnose this, let me
> > know and I can provide it. ?Thanks for any help.
> 
> Thanks for reporting this. If you say "infinite recursion", is there anything
> that indicates an actual recursion? Or does it just hang? Can you invoke
> the command above with an additional "-debug p" and show me the
> output?

I have no direct evidence that it was an infinite recursion.  It was
just a guess by the symptoms, but admittedly I have little knowledge
of Chicken's internals.  Sorry for the noise on that.  The symptoms
are that CPU usage increases to max, memory usage increases steadily,
and the process appears to hang.

Adding "-debug p" produces no output, even when removing "-quiet".
When I remove "-no-trace" and add "-debug p" it also fails in the same
way.  But when I remove both "-no-trace" and "-debug p" it works.  So
it fails when "-no-trace" and/or "-debug p" is specified, but works OK
when neither is specified.

Thanks,

-- 
Taylor Christopher Venable
http://real.metasyntax.net:2357/




reply via email to

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