unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Subject: Any known problems with 1.4, (read-enable 'positions) and debugging?
Date: Wed, 13 Mar 2002 17:49:44 -0600	[thread overview]
Message-ID: <87zo1cf2p3.fsf@raven.i.defaultvalue.org> (raw)


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.

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2002-03-13 23:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 23:49 Rob Browning [this message]
2002-03-16  8:17 ` Any known problems with 1.4, (read-enable 'positions) and debugging? Dirk Herrmann
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=87zo1cf2p3.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.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).