From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Cc: bug-guile@gnu.org
Subject: Re: stack overflow
Date: Wed, 16 Jul 2008 14:34:04 +0200 [thread overview]
Message-ID: <87mykihutf.fsf@gnu.org> (raw)
In-Reply-To: 87prukog9w.fsf@ossau.uklinux.net
Hi,
Neil Jerram <neil@ossau.uklinux.net> writes:
> Below is a proposed patch to do this. When and if this gets deployed,
> the third arg to %calibrate-stack-depth would be removed, so that it
> doesn't generate any output. But for now it's interesting to see what
> results people on various OSs get.
>
> Could people who've being getting "Stack overflow" errors try this
> out, and also report (for interest) the ";; Stack calibration" line
> that they get?
I think time has come to integrate this patch as it's proved to fix
things for various people. I tried it on several platforms, always
compiling with the default flags, i.e., `-O2'. Here's what I got[*]:
* i686-pc-linux-gnu, GCC 4.2.4
;; Stack calibration: (x1 x2 y1 y2 m c) = (170 690 170 690 1.0 0.0)
* x86_64-unknown-linux-gnu, GCC 4.1.2
;; Stack calibration: (x1 x2 y1 y2 m c) = (170 690 41 181 0.269230769230769 -4.76923076923077)
* sparc64-unknown-linux-gnu, GCC 4.1.3
;; Stack calibration: (x1 x2 y1 y2 m c) = (170 690 178 498 0.615384615384615 73.3846153846154)
* hppa2.0w-hp-hpux11.11,
HP92453-01 B.11.X.36086-36089-36092.GP HP C Compiler (cc)
;; Stack calibration: (x1 x2 y1 y2 m c) = (170 690 352 1472 2.15384615384615 -14.1538461538462)
* ia64-unknown-linux-gnu (itanium2), GCC 4.1.2
;; Stack calibration: (x1 x2 y1 y2 m c) = (170 690 10 50 0.0769230769230769 -3.07692307692308)
* i386-unknown-freebsd6.2, GCC 3.4.6
;; Stack calibration: (x1 x2 y1 y2 m c) = (170 690 114 394 0.538461538461538 22.4615384615385)
`pre-inst-guile' reaches the REPL in all cases, except on IA64 where it
stack-overflows (further investigation needed).
I'll comment the patch itself later on.
Thanks,
Ludovic.
[*] I really need to find a way to automate this. If anyone knows of
existing tools that would facilitate it (connecting to each machine,
running `configure', `make', etc.), please let me know. Otherwise,
I guess it wouldn't be too hard to write a script to do that.
prev parent reply other threads:[~2008-07-16 12:34 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
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 [this message]
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=87mykihutf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@gnu.org \
--cc=guile-devel@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).