[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-mit-scheme] [bug #36429] Compiler mysteriously runs out of stac
From: |
Alexey Radul |
Subject: |
Re: [Bug-mit-scheme] [bug #36429] Compiler mysteriously runs out of stack space |
Date: |
Wed, 11 Jul 2012 10:58:30 -0400 |
This bug is not impeding me in any way, so I leave the question of
fixing it entirely to your discretion. But thanks for finding out
what it was :)
~Alexey
On Wed, Jul 11, 2012 at 1:05 AM, Taylor R Campbell <address@hidden> wrote:
> Date: Mon, 07 May 2012 21:21:02 +0000
> From: Alexey Radul <address@hidden>
>
> Now, the enclosed file does contain a mistake: one of the procedures
> defined therein always recursively calls itself (and even not in
> tail position). However, my attempts to produce a small example
> using this to cause the compiler to run out of stack failed. I also
> got very confused when I tried to reduce the present example,
> because commenting out a form I would not have expected to have
> anything to do with anything caused the misbehavior to disappear.
>
> Hitting C-c C-b at exactly the right moment reveals that the compiler
> is deep into recursively generating debug data for an environment
> hierarchy that an earlier pass has decided to put a cycle into. (Some
> hierarchy!)
>
> As for how the cycle got there in the first place, well, have you read
> the comment at the top of closan.scm?
>
> I'm not sure it's worthwhile to spend many more brain cycles fixing
> these bugs in LIAR, though; the code is too highly interrelated to
> reason clearly about it or automatically any parts of it in isolation.