From: Rob Browning <rlb@defaultvalue.org>
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 11:40:38 -0600 [thread overview]
Message-ID: <87hengbecp.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0203160913410.29220-100000@marvin.ida.ing.tu-bs.de> (Dirk Herrmann's message of "Sat, 16 Mar 2002 09:17:58 +0100 (MET)")
Dirk Herrmann <dirk@ida.ing.tu-bs.de> writes:
> 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.
OK, so this isn't the same as SCM_DEBUG_CELL_ACCESSES...
> BTW, I always run the test suite with that setting.
If you happen to know, what's the relationship between
--enable-guile-debug and SCM_DEBUG? Is there any, and would it be
appropriate to have an --enable flag for this? I'd be happy to
specify using the flag in RELEASE as part of the testing process,
though I'd have to specify testing both with and without it since most
people won't want SCM_DEBUG for normal compiles.
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
prev parent reply other threads:[~2002-03-16 17:40 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
2002-03-16 17:40 ` Rob Browning [this message]
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=87hengbecp.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).