From: Dirk Herrmann <dirk@ida.ing.tu-bs.de>
Cc: Guile Development List <guile-devel@gnu.org>
Subject: Re: Any known problems with 1.4, (read-enable 'positions) and debugging?
Date: Sat, 16 Mar 2002 09:17:58 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.4.21.0203160913410.29220-100000@marvin.ida.ing.tu-bs.de> (raw)
In-Reply-To: <87zo1cf2p3.fsf@raven.i.defaultvalue.org>
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
next prev parent reply other threads:[~2002-03-16 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 23:49 Any known problems with 1.4, (read-enable 'positions) and debugging? Rob Browning
2002-03-16 8:17 ` Dirk Herrmann [this message]
2002-03-16 17:40 ` Rob Browning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0203160913410.29220-100000@marvin.ida.ing.tu-bs.de \
--to=dirk@ida.ing.tu-bs.de \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).