From: Albert Chin <guile-devel@mlists.thewrittenword.com>
To: guile-devel@gnu.org
Subject: Re: ERROR: Stack overflow from 1.8.6 on HP-UX 11.23/IA, 11.31/IA
Date: Tue, 24 Mar 2009 20:04:39 -0500 [thread overview]
Message-ID: <20090325010438.GA18990@songoku.il.thewrittenword.com> (raw)
In-Reply-To: <87skl2skzw.fsf@arudy.ossau.uklinux.net>
On Tue, Mar 24, 2009 at 08:50:59PM +0000, Neil Jerram wrote:
> Albert Chin <guile-devel@mlists.thewrittenword.com> writes:
>
> >> 1. Do all of the standalone tests fail with a stack overflow, or just
> >> those two?
> >
> > Unknown. Some of the tests fail to dlopen some modules:
> > ERROR: In procedure dynamic-link:
> > ERROR: file: "libguile-srfi-srfi-1-v-3", message: "can't open the module"
> > FAIL: test-require-extension
> > ...
> > ERROR: In procedure dynamic-link:
> > ERROR: file: "libtest-asmobs", message: "can't open the module"
> > FAIL: test-asmobs
> >
> > I haven't looked into why.
>
> Looks like not being up to pick up uninstalled libraries. You may
> like to use strace (or similar) to investigate where the system is
> looking, and see if there's a way to tell it to look in libguile. (We
> try to do this with the LTDL_LIBRARY_PATH variable, but perhaps that
> isn't working on HP-UX?)
I'll look into it.
> >> 2. Can you send us your libguile/stack-limit-calibration.scm?
> >
> > Attached.
>
> OK, so there's a factor of 3 there. Can you try changing the hardcode
> stack limit in eval.c from 20000 to 60000, and see if that allows the
> affected tests to pass? If it does, we'll have to find a way of
> applying the factor in libguile/stack-limit-calibration.scm before
> Guile starts booting.
Bumping the stack limit to 60000 solved the problem.
--
albert chin (china@thewrittenword.com)
prev parent reply other threads:[~2009-03-25 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 21:47 ERROR: Stack overflow from 1.8.6 on HP-UX 11.23/IA, 11.31/IA Albert Chin
2009-03-12 21:56 ` Albert Chin
2009-03-13 9:25 ` Ludovic Courtès
2009-03-14 12:38 ` Neil Jerram
2009-03-16 6:44 ` Albert Chin
2009-03-24 20:50 ` Neil Jerram
2009-03-25 1:04 ` Albert Chin [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=20090325010438.GA18990@songoku.il.thewrittenword.com \
--to=guile-devel@mlists.thewrittenword.com \
--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).