Mark H Weaver m...@netris.org 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 me
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
According to node User level options interfaces of api-options.texi,
(debug-options 'full) should print a list of options, but it fails
with ERROR: unbound variable: option-name. The other options
interfaces (eval-options, read-options, print-options, traps) are
broken as well.
The problem is
Hi all,
I finally started real work on implementing the elisp compiler and just
pushed a first start-off code to branch elisp. It is however not yet
usable for anything, but also already has some very few things done.
Some important points I'd like to mention and welcome comments:
1) In
On Tue 09 Jun 2009 20:47, Mark H Weaver m...@netris.org 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.
On Tue 09 Jun 2009 21:27, Mark H Weaver m...@netris.org writes:
According to node User level options interfaces of api-options.texi,
(debug-options 'full) should print a list of options, but it fails
with ERROR: unbound variable: option-name. The other options
interfaces (eval-options,
Howdy,
On Tue 09 Jun 2009 22:07, Daniel Kraft d...@domob.eu writes:
I finally started real work on implementing the elisp compiler and just
pushed a first start-off code to branch elisp. It is however not yet
usable for anything, but also already has some very few things done.
Yay!! I hope
Andy Wingo wi...@pobox.com 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
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:
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 larger
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
11 matches
Mail list logo
