From: Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de>
Cc: guile-devel@gnu.org
Subject: Re: Purify on Guile
Date: Wed, 19 Nov 2003 11:28:46 +0100 [thread overview]
Message-ID: <uw5ptfo1wkh.fsf@merkur.math.uni-magdeburg.de> (raw)
In-Reply-To: <3FBB34A9.2020404@synopsys.com> (pavane.luo@synopsys.COM's message of "Wed, 19 Nov 2003 17:15:21 +0800")
yluo <pavane.luo@synopsys.COM> writes:
> We use memory-debugging tools (Purify) here, and it is annoying to get
> Error/Warning messages every time. There are many SBR and UMR warnings
> during garbage collection and some SBW (Stack array bounds write)
> errors reported during dynamic throw. I guess those operations on
> memory are harmless, but which always makes people nervous.
Guile's conservative garbage collector scans memory regions for valid
pointers. It may hit uninitialized memory cells during the scan.
This is normal.
I have not seen warnings about SBW, though. (I use Purify on
SPARC/Solaris.) They are probably due to the stack unwinding that is
done at a throw.
> Is there any way to avoid those happened? If so, could you please
> kindly point me the way?
Simply suppress these warnings. Here are three suppressions from my
.purify file.
suppress umr scm_ceval
suppress umr scm_mark_locations
suppress sbr scm_mark_locations
--
Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-11-19 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 9:15 Purify on Guile yluo
2003-11-19 10:28 ` Matthias Koeppe [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=uw5ptfo1wkh.fsf@merkur.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.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).