From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Roland Orre Newsgroups: gmane.lisp.guile.user Subject: Debugging hints wanted Date: Mon, 30 Jun 2008 18:56:22 +0200 Message-ID: <1214844983.6032.96.camel@localhost.localdomain> References: <20080204171945.4175db40@altosw.be> <20080204214003.GB2646@stratocaster.home> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1214845010 3657 80.91.229.12 (30 Jun 2008 16:56:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Jun 2008 16:56:50 +0000 (UTC) To: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Jun 30 18:57:36 2008 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KDMgx-00061G-Rj for guile-user@m.gmane.org; Mon, 30 Jun 2008 18:57:28 +0200 Original-Received: from localhost ([127.0.0.1]:55730 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KDMg7-00062d-Ei for guile-user@m.gmane.org; Mon, 30 Jun 2008 12:56:35 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KDMg3-000621-0o for guile-user@gnu.org; Mon, 30 Jun 2008 12:56:31 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KDMfz-00060F-9O for guile-user@gnu.org; Mon, 30 Jun 2008 12:56:29 -0400 Original-Received: from [199.232.76.173] (port=54170 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KDMfz-000605-5t for guile-user@gnu.org; Mon, 30 Jun 2008 12:56:27 -0400 Original-Received: from csmtp1.one.com ([195.47.247.21]:47121 helo=csmtp1.b-one.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KDMfy-0007TY-Nm for guile-user@gnu.org; Mon, 30 Jun 2008 12:56:26 -0400 Original-Received: from dyna224-183.nada.kth.se (dyna224-183.nada.kth.se [130.237.224.183]) by csmtp1.b-one.net (Postfix) with ESMTP id C906E9882632; Mon, 30 Jun 2008 18:56:24 +0200 (CEST) In-Reply-To: <20080204214003.GB2646@stratocaster.home> X-Mailer: Evolution 2.6.1 X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:6616 Archived-At: I need hints on how to find occasional segmentation faults and missed GC references. This relates to 64 bit machines. Background: When I started using 64 bit machines a few years ago most of guile fine after I converted my modules to 64 bit code. Apart from changes in my own C-code the only thing I changed in guile was size of uvect,ivect in unif.c cells as they by default become 64 bit long instead of 32 bit. My 64 bits are dual-CPU/core though so it may be related to that (still using guile 1.7) but I don't have any problem on dual CPU 32 bits systems. My modules have worked perfectly fine on 32 bit machines but on 64 bits I occasionally get something like # if I run that code fast, which indicates a threading problem (I do not use threads in this case, but seems like guile does). This does not occur if I run guile through gdb. This happens not too often but it seems to be related to string->symbol symbol->string. My bigger problem though is frequently occurring segmentation faults or otherwise corrupt pointers. If I then run the code in gdb I can get Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x2ae316e4f070 (LWP 6699)] 0x00002ae314b9d091 in scm_gc_mark_dependencies (p=0x97c) at gc-mark.c:441 441 if (SCM_GC_MARK_P (ptr)) Current language: auto; currently c Grateful for any hints to trace these kinds of problems. Roland Orre