From: "Neil Jerram" <neiljerram@googlemail.com>
To: tantalum <theseph@gmx.de>
Cc: bug-guile@gnu.org
Subject: Re: guile 1.8.5 compile segfault
Date: Mon, 13 Oct 2008 23:38:51 +0100 [thread overview]
Message-ID: <49dd78620810131538n52a93268j7175d82d3986916a@mail.gmail.com> (raw)
In-Reply-To: <48D936F5.2070409@gmx.de>
Sorry to take a while to continue this investigation.
2008/9/23 tantalum <theseph@gmx.de>:
>
> i managed to get a core dump file. heres a backtrace and some "frame x"
> calling:
> http://pastebin.com/m3c55053b
This:
(gdb) frame 0
#0 scm_mark_locations (x=0x7fff7f4c8d68, n=18446744073709551561) at
gc-mark.c:435
435 SCM obj = * (SCM *) &x[m];
(gdb) frame 1
#1 0x00002b802b8a66ed in scm_threads_mark_stacks () at threads.c:1390
1390 scm_mark_locations (t->base, t->top - t->base);
really does indicate a problem with SCM_STACK_GROWS_UP. The relevant
code in scm_threads_mark_stacks () is:
#if SCM_STACK_GROWS_UP
scm_mark_locations (t->base, t->top - t->base);
#else
scm_mark_locations (t->top, t->base - t->top);
#endif
so SCM_STACK_GROWS_UP must be defined and non-zero.
The definition of SCM_STACK_GROWS_UP is in libguile/scmconfig.h (which
is itself generated during configuration). Could you check what you
have there?
> to compile guile 1.8.5 (release or snapshot-0923) on this i386 other
> machine, i need to apply this patch, found via google:
> http://pastebin.com/m6226ece1
> otherwise it stops leaving its long message, end of which is:
> http://pastebin.com/m102992ca
This one is a known problem from using Libtool 2.2. We currently
build and test Guile with Libtool 1.5.22, and are aware that there are
issues with using 2.2 instead - such as this one.
Regards,
Neil
next prev parent reply other threads:[~2008-10-13 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 18:35 guile 1.8.5 compile segfault tantalum
2008-10-13 22:38 ` Neil Jerram [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-22 17:25 tantalum
2008-09-22 19:29 ` Neil Jerram
2008-09-21 13:01 tantalum
2008-09-21 21:27 ` Neil Jerram
2008-09-20 13:31 tantalum
2008-09-21 9:43 ` Neil Jerram
2008-09-19 16:14 tantalum
2008-09-19 22:48 ` Neil Jerram
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=49dd78620810131538n52a93268j7175d82d3986916a@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=bug-guile@gnu.org \
--cc=theseph@gmx.de \
/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).