From: Andy Wingo <wingo@pobox.com>
To: Hans Aberg <haberg-1@telia.com>
Cc: bug-guile bug <bug-guile@gnu.org>
Subject: Re: Guile 2.0.1: scm_init_guile() broken on Mac OS X 10.6.7
Date: Fri, 20 May 2011 15:10:12 +0200 [thread overview]
Message-ID: <m3d3jdwma3.fsf@unquote.localdomain> (raw)
In-Reply-To: <8B1A6BFD-DB61-4072-A96C-9AC25F0DC6C1@telia.com> (Hans Aberg's message of "Fri, 20 May 2011 13:31:42 +0200")
On Fri 20 May 2011 13:31, Hans Aberg <haberg-1@telia.com> writes:
> On 20 May 2011, at 12:11, Andy Wingo wrote:
>
>>> On Mac OS X 10.6.7, compiled using Xcode Version 3.2.6 64-bit,
>>> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1, scm_init_guile() gives the
>>> error:
>>>
>>> Failed to get stack base for current thread.
> ...
>> As you can see we rely on libgc here, and so this is a libgc bug. Can
>> you try a newer libgc, or if that still fails, bring it up on their
>> list?
>
> On Mac OS X, one must call GC_init() (not necessary on GNU/Linux). Has
> that dropped out in guile-2.0.1?
I really have no idea. As you see in 2.0.1 we rely on libgc for
detecting stack boundaries in the non-scm_with_guile case, as is
appropriate I think. As for GC_init() I don't know, and would be
surprised if that were the case.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-20 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87aafb2w68.fsf@gnu.org>
2011-05-15 10:56 ` Guile 2.0.1: scm_init_guile() broken on Mac OS X 10.6.7 Hans Aberg
2011-05-20 10:11 ` Andy Wingo
2011-05-20 10:52 ` Hans Aberg
2011-05-20 11:31 ` Hans Aberg
2011-05-20 13:10 ` Andy Wingo [this message]
2011-05-20 13:39 ` Hans Aberg
2011-05-20 13:58 ` Andy Wingo
2011-05-20 16:21 ` Hans Aberg
2011-05-21 12:58 ` Hans Aberg
2011-05-21 17:20 ` Hans Aberg
2011-06-17 9:26 ` Andy Wingo
2011-06-17 15:58 ` Hans Aberg
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=m3d3jdwma3.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=haberg-1@telia.com \
/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).