unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: stack overflow
Date: Wed, 13 Feb 2008 10:05:20 +0100	[thread overview]
Message-ID: <87tzkd8bvz.fsf@gnu.org> (raw)
In-Reply-To: 47B2A8DF.9070004@tammer.net

Hi Rainer,

Rainer Tammer <tammer@tammer.net> writes:

> I tried to build GUILE 1.8.3 on AIX 6.1 with the IBM XL C/C++ 9.0 compiler.
> During the build I get the following error:
>
>
> ./guile_filter_doc_snarfage --filter-snarfage) > regex-posix.doc || {

[...]

> In /daten/source/test/guile-1.8.3/ice-9/null.scm:
>  20: 76* (define-module (ice-9 null) :use-module ...)
> In unknown file:
>   ?: 77* [copy-tree ...
>   ?: 78* [apply #<procedure #f args> ((ice-9 null) :use-module (ice-9 
> syncase) ...)]
>   ?: 79  [#<procedure #f args> (ice-9 null) :use-module ...]
>   ?: 80  (quasiquote (eval-case (# #) (else #)))
>   ?: 81* [compile-define-module-args ((ice-9 null) :use-module (ice-9 
> syncase) ...)]
>   ?: 82  ((letrec ((loop #)) loop) (quasiquote ((quote #))) (cdr args))
>   ?: 83* (letrec ((loop (lambda # #))) loop)
>   ?: 84* (lambda (compiled-args args) (cond (# #) (# #) (# #) ...))
>
> <unnamed port>: In expression (lambda (compiled-args args) (cond # # ...)):
> <unnamed port>: Stack overflow

A couple of ideas:

  1. What `CFLAGS' are you using?  In particular, are optimizations
     enabled?

     With GCC, compiling without optimizations usually yields a Guile
     that stack-overflows because the evaluator would use so much stack
     space that the default stack limit is quickly hit.  You could have
     the same problem with IBM's xlc, so make sure to enable
     optimizations.

     Actually, `configure' only adds `-O2' when GCC is being used, so
     I'm pretty sure it's up to you to pass `configure' or `make' the
     right CFLAGS, e.g.,

       CFLAGS="-the-option-that-enables-optimizations" ./configure

     If that fixes the problem, then we can change `configure' to use,
     e.g., `AX_COMPILER_VENDOR' [0] to automatically add optimization
     options that correspond to the compiler being used.

  2. Is it a 64-bit platform?

     If so, it may be the case that the default stack limit (see
     `debug-options') is about two times smaller than what you need.

Thanks,
Ludovic.

[0] http://autoconf-archive.cryp.to/ax_compiler_vendor.html





  reply	other threads:[~2008-02-13  9:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  8:22 stack overflow Rainer Tammer
2008-02-13  9:05 ` Ludovic Courtès [this message]
2008-02-13  9:15   ` Ludovic Courtès
2008-02-13 11:46     ` Rainer Tammer
2008-02-13 12:49       ` Ludovic Courtès
2008-02-14  7:36         ` stack overflow / partial success Rainer Tammer
2008-02-14  8:38           ` Ludovic Courtès
2008-02-18  6:11             ` Rainer Tammer
2008-02-18  8:33               ` Ludovic Courtès
2008-02-18  9:56                 ` Rainer Tammer
2008-02-18 10:37                   ` Ludovic Courtès
2008-02-18 14:00                     ` Rainer Tammer
2008-02-18 14:11                       ` Ludovic Courtès
2008-02-19  7:15                         ` Rainer Tammer
2008-02-19 21:53                           ` Ludovic Courtès
2008-02-20  8:18                             ` Rainer Tammer
2008-02-20  9:28                             ` Rainer Tammer
2008-02-20 14:40                             ` GUILE 1.8.4 on AIX 6.1 Rainer Tammer
     [not found]         ` <87wsp83807.fsf@ossau.uklinux.net>
     [not found]           ` <871w7fore8.fsf@gnu.org>
     [not found]             ` <66e540fe0802140226k3cd96c46x286ac753bbb2b8b7@mail.gmail.com>
     [not found]               ` <87ejbfg4pr.fsf@gnu.org>
     [not found]                 ` <66e540fe0802140339n2121e1d9y85fcc9f019d8be0f@mail.gmail.com>
2008-02-25 21:52                   ` stack overflow Neil Jerram
2008-07-16 12:34                     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tzkd8bvz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).