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: how does one debug a SEGV in scm_threads_prehistory? Date: Wed, 18 Jun 2008 15:29:02 -0400 Message-ID: References: <668c430c0806180937g7fd824e8m7a871340d480599a@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1213817362 27455 80.91.229.12 (18 Jun 2008 19:29:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 18 Jun 2008 19:29:22 +0000 (UTC) Cc: guile-devel@gnu.org To: "Bruce Korb" Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Wed Jun 18 21:30:06 2008 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K93M3-0003ze-0p for guile-devel@m.gmane.org; Wed, 18 Jun 2008 21:30:03 +0200 Original-Received: from localhost ([127.0.0.1]:34843 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K93LE-00018v-8p for guile-devel@m.gmane.org; Wed, 18 Jun 2008 15:29:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K93LB-000184-AQ for guile-devel@gnu.org; Wed, 18 Jun 2008 15:29:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K93L9-00017s-TF for guile-devel@gnu.org; Wed, 18 Jun 2008 15:29:09 -0400 Original-Received: from [199.232.76.173] (port=59487 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K93L9-00017p-Qc for guile-devel@gnu.org; Wed, 18 Jun 2008 15:29:07 -0400 Original-Received: from fnord.ir.bbn.com ([192.1.100.210]:60810) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K93L4-0002eC-VH; Wed, 18 Jun 2008 15:29:03 -0400 Original-Received: by fnord.ir.bbn.com (Postfix, from userid 10853) id 3602552EA; Wed, 18 Jun 2008 15:29:02 -0400 (EDT) X-Hashcash: 1:20:080618:guile-devel@gnu.org::mHe+bvIGqBrI8pZ2:0000000000000000000000000000000000000000001Rxm X-Hashcash: 1:20:080618:bkorb@gnu.org::0JynIr03bH/pywd0:00002kZi In-Reply-To: <668c430c0806180937g7fd824e8m7a871340d480599a@mail.gmail.com> (Bruce Korb's message of "Wed, 18 Jun 2008 09:37:57 -0700") User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/22.1 (berkeley-unix) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:7330 Archived-At: Our main development server was "upgraded" to 64 bits, but mostly still runs 32 bit software, so this is from a 32 bit build on a 64 bit platform. Naturally, this all works on 32 on 32 and on 64 on 64. But with 32 on 64, not so well: I presume you are talking about Linux and going from i386 to amd64/x86_64 (not sure which name is used in Linux). I would be suspicious that the i386 binary is getting linked with some amd64 libs somehow - to first order it would seem to be an OS bug if the emulated i386 binary doesn't run the same as on i386. But I could certainly see an allowable difference leading to triggering a latent bug in guile. Can you trigger this with a simple example? I have i386 and now amd64 boxes, and would be curious to try the NetBSD i386 binary on amd64, as well as native.