From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Dirk Herrmann Newsgroups: gmane.lisp.guile.devel Subject: Re: Any known problems with 1.4, (read-enable 'positions) and debugging? Date: Sat, 16 Mar 2002 09:17:58 +0100 (MET) Sender: guile-devel-admin@gnu.org Message-ID: References: <87zo1cf2p3.fsf@raven.i.defaultvalue.org> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1016267513 12633 127.0.0.1 (16 Mar 2002 08:31:53 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sat, 16 Mar 2002 08:31:53 +0000 (UTC) Cc: Guile Development List Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16m9bV-0003Hf-00 for ; Sat, 16 Mar 2002 09:31:53 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16m9Rf-0006DC-00; Sat, 16 Mar 2002 03:21:43 -0500 Original-Received: from marvin.ida.ing.tu-bs.de ([134.169.132.60]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16m9OD-0005v5-00 for ; Sat, 16 Mar 2002 03:18:09 -0500 Original-Received: from localhost (dirk@localhost) by marvin.ida.ing.tu-bs.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id g2G8HxT29504; Sat, 16 Mar 2002 09:18:00 +0100 X-Authentication-Warning: marvin.ida.ing.tu-bs.de: dirk owned process doing -bs Original-To: Rob Browning In-Reply-To: <87zo1cf2p3.fsf@raven.i.defaultvalue.org> Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:83 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:83 On Wed, 13 Mar 2002, Rob Browning wrote: > > I was trying to track down a problem in some code using 1.4, so I > turned on > > --with-threads \ > --enable-debug-freelist \ > --enable-debug-malloc \ > --enable-guile-debug > > and I edited configure.in to add > > CFLAGS="$CFLAGS -DSCM_DEBUG_CELL_ACCESSES=1" > > I also added to the code I was trying to test: > > (debug-enable 'backtrace) > (debug-enable 'debug) > (read-enable 'positions) > > Then with this debugging 1.4, I ran in to a new failure (not the one I > was originally trying to diagnose) that looked like this > > 3 segments total (2:6006, 1:46023, 1:24012) > 996 2-cells in segment 0 > 3 segments total (2:6006, 1:46023, 1:24012) > 996 2-cells in segment 0 > Bad cell in freelist on newcell 321632: 0'th elt > > After some experimentation, I found that if I commented out the > (read-enable 'positions) command, the newcell problem vanished. > > Any idea why? Is this a known issue, or is 'positions not likely to > be related to the problem. Just to let you know, you can get (hopefully) much closer to the source of such heap problems if you compile guile using make CFLAGS="-g -O2 -Wall -W -DSCM_DEBUG=1" and then run your examples. This enables a lot of checks, one of which is to check every cell that is accessed for being valid. BTW, I always run the test suite with that setting. Best regards Dirk Herrmann _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel