From: Greg Troxel <gdt@ir.bbn.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: boehm-gc troubles with 2.0.11 on NetBSD/i386
Date: Tue, 22 Apr 2014 09:01:56 -0400 [thread overview]
Message-ID: <rmippk9msaj.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: 87eh13fs6a.fsf@yeeloong.lan
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
A partial update:
I am using 2.0.11 now.
After updating to libgc 7.4.0, I have the same problem with a similar
stack trace. libgc is built without threads and passes it's "gmake
check".
I have the same problem with libgc 7.4.0 on netbsd-5/i386 (libgc
passes gmake check on this combination also).
On netbsd-5/i386, I tried to build libgc and guile with threads, but
it failed to link with tls_get_addr. This is likely a known lack of
support in netbsd-5 which AFAIK doesn't provide thread-local storage.
I haven't yet compiled libgc and guile with debugging symbols and
without optimization; I realize that's what I need to do to figure
this out. I read a bit of the code to get started understanding the
boot sequence.
It seems there is detection of stack growth detection. I wonder if
that's somehow going astray.
I am curious if others are having success on other *BSD, and which
versions and architectures.
[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2014-04-22 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 13:14 boehm-gc troubles with 2.0.10 on NetBSD/i386 Greg Troxel
2014-04-11 17:21 ` Mark H Weaver
2014-04-11 18:14 ` Greg Troxel
2014-04-11 19:09 ` Mark H Weaver
2014-04-11 19:39 ` Greg Troxel
2014-04-11 21:54 ` Mark H Weaver
2014-04-22 13:01 ` Greg Troxel [this message]
2014-04-22 14:39 ` boehm-gc troubles with 2.0.11 " Taylan Ulrich Bayirli/Kammer
2014-04-22 16:14 ` Mark H Weaver
2014-09-20 6:16 ` In-Ho Yi
2014-09-20 23:25 ` Mark H Weaver
2014-04-12 10:16 ` boehm-gc troubles with 2.0.10 " Ludovic Courtès
2014-04-12 17:06 ` Mark H Weaver
2014-04-12 23:56 ` Greg Troxel
2014-04-12 10:15 ` 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=rmippk9msaj.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).