From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ludo@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) Newsgroups: gmane.lisp.guile.user Subject: Re: Debugging hints wanted Date: Mon, 30 Jun 2008 21:42:29 +0200 Message-ID: <87zlp2g15m.fsf@gnu.org> References: <20080204171945.4175db40@altosw.be> <20080204214003.GB2646@stratocaster.home> <1214844983.6032.96.camel@localhost.localdomain> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1214854989 5912 80.91.229.12 (30 Jun 2008 19:43:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Jun 2008 19:43:09 +0000 (UTC) To: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Jun 30 21:43:55 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 1KDPHp-0004pe-BJ for guile-user@m.gmane.org; Mon, 30 Jun 2008 21:43:41 +0200 Original-Received: from localhost ([127.0.0.1]:60785 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KDPGy-0000xT-UB for guile-user@m.gmane.org; Mon, 30 Jun 2008 15:42:49 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KDPGu-0000xJ-UJ for guile-user@gnu.org; Mon, 30 Jun 2008 15:42:45 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KDPGt-0000wn-0O for guile-user@gnu.org; Mon, 30 Jun 2008 15:42:44 -0400 Original-Received: from [199.232.76.173] (port=49269 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KDPGs-0000wk-PJ for guile-user@gnu.org; Mon, 30 Jun 2008 15:42:42 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:48572 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KDPGs-0002EX-DI for guile-user@gnu.org; Mon, 30 Jun 2008 15:42:42 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KDPGm-0004af-Pd for guile-user@gnu.org; Mon, 30 Jun 2008 19:42:36 +0000 Original-Received: from reverse-83.fdn.fr ([80.67.176.83]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Jun 2008 19:42:36 +0000 Original-Received: from ludo by reverse-83.fdn.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Jun 2008 19:42:36 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 39 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: reverse-83.fdn.fr X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 13 Messidor an 216 de la =?iso-8859-1?Q?R=E9volution?= X-PGP-Key-ID: 0xEA52ECF4 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 821D 815D 902A 7EAB 5CEE D120 7FBA 3D4F EB1F 5364 X-OS: i686-pc-linux-gnu User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) Cancel-Lock: sha1:2Kc/KFnVqtFuZ2X0M74TQO491YU= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:6617 Archived-At: Hi, Roland Orre writes: > I need hints on how to find occasional segmentation faults > and missed GC references. This relates to 64 bit machines. Is it x86-64, IA64, or something else? The Git repository (the future 1.8.6) contains an important bug fix for IA64. I think there were x86-64-related during the 1.8.x series, too. Thus, I'd suggest using the latest Guile on these platforms. > 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. Is it reproducible? > 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 Likewise, is it reproducible? Can you show the full backtrace (it should show where 0x97c comes from)? Hope this helps, Ludovic.