Mark H Weaver writes:
> Apologies for sending so many emails in so short a time, but I've put
> together the final pieces of this puzzle.
Fantastic puzzling!
With Andy's change to increase the default stack limit to 16,
`make check' passes for me now. I've also unblocked the overnight
snap
Andy Wingo writes:
> On Tue 09 Jun 2009 20:47, Mark H Weaver writes:
>
>> To generate the backtrace, I added the following lines near the top of
>> guile-tools. Is there a better way?
>>
>> (debug-enable 'debug)
>> (debug-enable 'backtrace)
>> (debug-set! depth 100)
>> (write (debug-opt
Apologies for sending so many emails in so short a time, but I've put
together the final pieces of this puzzle.
GNU Make 3.81, the version in Debian lenny, sets the stack soft limit
to match the hard limit "so that alloca does not fail". On my system,
the default stack hard limit is infinite, so
I wrote:
> > (show-file-name #t stack 4 debug backtrace depth 100 maxdepth 1000
> > frames 3 indent 10 width 79 procnames cheap)
>
> Notice the "stack 4", which means that the stack limit (as far as
> guile is concerned) is only 4 words, i.e. 160 kilobytes. Other
> times, I see much
Earlier, I wrote:
> Strangely, the stack overflow doesn't happen when I run the compile
> command (as echoed by make) directly from the command line. I only
> see it happen when compiling via make.
I just noticed something. Look at the result of (debug-options) in
the first backtrace I sent:
>
Andy Wingo wrote:
> BTW I pushed something that might affect
> the stack overflow issue, can you give that a try? I have one report of
> it working where it didn't use to work.
It still overflows the stack on my system, but since you changed the
order of compilation, it now fails on a different f
On Tue 09 Jun 2009 20:47, Mark H Weaver writes:
> On Tue, Jun 09, 2009 at 09:27:37AM +0200, Andy Wingo wrote:
>> It's a strange thing, and I don't see it on my x86-32 laptop running
>> Fedora. But I've heard reports of this. A backtrace at the time of stack
>> overflow would be helpful.
>
> Stran
On Tue, Jun 09, 2009 at 09:27:37AM +0200, Andy Wingo wrote:
> It's a strange thing, and I don't see it on my x86-32 laptop running
> Fedora. But I've heard reports of this. A backtrace at the time of stack
> overflow would be helpful.
Strangely, the stack overflow doesn't happen when I run the com
Mark H Weaver wrote:
> On Tue, Jun 09, 2009 at 12:24:48AM +0100, Neil Jerram wrote:
> > > GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
> > > "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> > > ERROR: Stack overflow
> >
> > This is still happening for
On Tue 09 Jun 2009 02:52, Mark H Weaver writes:
> On Tue, Jun 09, 2009 at 12:24:48AM +0100, Neil Jerram wrote:
>> > GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
>> > "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
>> > ERROR: Stack overflow
>>
>> This is stil
On Tue, Jun 09, 2009 at 12:24:48AM +0100, Neil Jerram wrote:
> > GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
> > "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> > ERROR: Stack overflow
>
> This is still happening for me after pulling the latest master today.
Neil Jerram writes:
> Unfortunately I'm not getting through `make' yet:
>
> ...
> GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
> "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> ERROR: Stack overflow
This is still happening for me after pulling the latest ma
On Sat 06 Jun 2009 15:19, l...@gnu.org (Ludovic Courtès) writes:
> Incidentally, I just did a `pull', and compiling the compiler appears to
> be much slower than in my recollections (pre-syncase merge, I think).
> Is it just an impression?
Nope, not just an impression, it's true. Reasons discusse
Hey,
Andy Wingo writes:
> I pushed support for automatic compilation in master. That is, whenever
> load-from-path sees that it should compile a file, and autocompilation
> is enabled, it compiles the file then and there.
Cool!
Incidentally, I just did a `pull', and compiling the compiler appe
Neil Jerram writes:
> ...
> GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o
> "language/ecmascript/spec.go" "language/ecmascript/spec.scm"
> ERROR: Stack overflow
>
> But if I switch to a shell and repeat with --debug, no problem:
>
> n...@arudy:~/SW/Guile/git/module$ GUILE_A
Andy Wingo writes:
> There's a lot of trickiness to this, but I think we all have instincts
> on how this should work. I'll write docs soon, but in the meantime, I
> would like for folks to ignore the implementation, and just use Guile
> for a while, and see if what it does sounds right to you. I
16 matches
Mail list logo
