From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: jseward@acm.org
Subject: guile.supp for valgrind
Date: Sun, 5 Jan 2003 19:54:31 +0100 [thread overview]
Message-ID: <15896.32615.902539.901236@blauw.xs4all.nl> (raw)
In-Reply-To: <3E1867F7.4E95CE4D@veritas.com>
bkorb@veritas.com writes:
> Thanks for valgrind!! It's wonderful.
> My box (SuSE Linux 8.0) has a Guile library with lots of
> problems. The attached suppression file pretty much gets
> rid of them. I don't know if they've fixed the issues
> after Guile-1.4, so I'm CC-ing them for their possible
> interest. I'm thinking that this should be incorporated
> into the default.supp when the Guile library version is 1.4.
GUILE does conservative garbage collection, which entails scanning
(possibly uninitialized) chunks of memory for possible pointers. The
valgrind errors are harmless.
Here's a suppression file for 1.6 and for 1.7 CVS
****************
1.6:
{
guilegc
Cond
fun:heap_segment
}
{
guilegc
Value4
fun:scm_mark_weak_vector_spines
}
{
guilegc
Cond
fun:scm_mark_weak_vector_spines
}
{
guilegc
Value4
fun:scm_scan_weak_vectors
}
{
guilegc
Cond
fun:scm_scan_weak_vectors
}
{
guilegc
Value4
fun:scm_gc_mark
}
{
guilegc
Cond
fun:scm_gc_mark
}
{
guilegc
Cond
fun:scm_gc_sweep
}
{
guilegc
Value4
fun:scm_markstream
}
{
guilegc
Cond
fun:scm_mark_locations
}
{
guilegc
Value4
fun:scm_markcdr
}
****************
guile 1.7 and later
# guile valgrind suppression file
{
guilegc
Value4
fun:scm_gc_mark_dependencies
}
{
guilegc
Value4
fun:scm_gc_mark
}
{
guilegc
Value4
fun:scm_i_find_heap_segment_containing_object
}
{
guilegc
Cond
fun:scm_i_find_heap_segment_containing_object
}
{
guilegc
Value4
fun:scm_markcdr
}
{
guilegc
Value4
fun:scm_mark_locations
}
{
guilegc
Cond
fun:scm_mark_locations
}
{
guilegc
Cond
fun:scm_gc_mark
}
{
guilegc
Cond
fun:scm_i_sweep_card
}
{
guilegc
Cond
fun:scm_mark_weak_vector_spines
}
{
guilegc
Cond
fun:scm_gc_mark_dependencies
}
{
guilegc
Cond
fun:scm_scan_weak_vectors
}
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-01-05 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 17:14 guile.supp for valgrind Bruce Korb
2003-01-05 18:54 ` Han-Wen Nienhuys [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=15896.32615.902539.901236@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--cc=jseward@acm.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).