From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Greg Troxel Newsgroups: gmane.lisp.guile.devel Subject: Re: boehm-gc troubles with 2.0.11 on NetBSD/i386 Date: Tue, 22 Apr 2014 09:01:56 -0400 Message-ID: References: <87mwfrg4to.fsf@yeeloong.lan> <87ioqffztd.fsf@yeeloong.lan> <87eh13fs6a.fsf@yeeloong.lan> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Trace: ger.gmane.org 1398171760 3396 80.91.229.3 (22 Apr 2014 13:02:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 22 Apr 2014 13:02:40 +0000 (UTC) Cc: guile-devel@gnu.org To: Mark H Weaver Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Apr 22 15:02:33 2014 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WcaLB-00035B-8c for guile-devel@m.gmane.org; Tue, 22 Apr 2014 15:02:25 +0200 Original-Received: from localhost ([::1]:55115 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WcaLA-0006K5-RQ for guile-devel@m.gmane.org; Tue, 22 Apr 2014 09:02:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51049) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WcaKy-0006Ay-Up for guile-devel@gnu.org; Tue, 22 Apr 2014 09:02:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WcaKs-0003Dt-Is for guile-devel@gnu.org; Tue, 22 Apr 2014 09:02:12 -0400 Original-Received: from fnord.ir.bbn.com ([192.1.100.210]:52983) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WcaKs-0003Df-DF for guile-devel@gnu.org; Tue, 22 Apr 2014 09:02:06 -0400 Original-Received: by fnord.ir.bbn.com (Postfix, from userid 10853) id 5F29DA858; Tue, 22 Apr 2014 09:02:05 -0400 (EDT) OpenPGP: id=32611E25 X-Hashcash: 1:20:140422:mhw@netris.org::FTd/GvGFvpt4MD+V:0000nXA X-Hashcash: 1:20:140422:guile-devel@gnu.org::+FI6kHlVjJcDMJG+:0000000000000000000000000000000000000000009NN6 User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.4 (berkeley-unix) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 192.1.100.210 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:17094 Archived-At: --=-=-= Content-Type: text/plain 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. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlNWaEQACgkQ+vesoDJhHiUd4ACeOKO/xZH9u08UuEoEVaZzxLSd g4YAniqnYQTa0xiHX4xsFvBM717rxWZG =guFB -----END PGP SIGNATURE----- --=-=-=--