unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Subject: Re: deprecated features
Date: Tue, 23 Jan 2007 23:45:14 +0100	[thread overview]
Message-ID: <45B68FFA.8070408@xs4all.nl> (raw)
In-Reply-To: <45B620B7.804@gnu.org>

Bruce Korb escreveu:
> By the way, have you all given any consideration to releasing a
> valgrind config file that would clean out valgrind chaff?
> I recently needed to do a valgrind run and it was quite painful.

I always use the file below.  I am not sure what the best way to
distribute it would be.


# guile valgrind suppression file
{
    	guilegc
	Memcheck:Value4
    	fun:scm_c_hook_run
}
{
    	guilegc
	Memcheck:Cond
    	fun:scm_c_hook_run
}

{
    guilegc
	Memcheck:Value4
    fun:scm_gc_mark_dependencies
}

{
    guilegc
	Memcheck:Cond
    fun:scan_weak_hashtables
}

{
	guilegc
 	Memcheck:Cond
	fun:scm_i_mark_weak_vectors_non_weaks
}

{
	guilegc
	Memcheck:Value4
 	fun:scm_i_symbol_mark
}
{
	guilegc
	Memcheck:Value4
	fun:scm_markstream
}

{
	guilegc
	Memcheck:Value4
 	fun:scm_i_string_mark
}
{
    guilegc
	Memcheck:Cond
    fun:scm_gc_mark_dependencies
}

{
    guilegc
    Memcheck:Cond
    fun:scm_i_scan_weak_hashtables
}

{
    guilegc
    Memcheck:Cond
    fun:scm_i_remove_weaks_from_weak_vectors
}

{
    guilegc
    Memcheck:Cond
    fun:scan_dynamic_states_and_fluids
		}

{

    guilegc	    
	Memcheck:Value4
    fun:scm_gc_mark
}
{

    guilegc	    
	Memcheck:Value4
    fun:scm_gc_mark
}

{
guilegc
Memcheck:Value4
fun:scm_i_find_heap_segment_containing_object
}

{
guilegc
Memcheck:Cond
fun:scm_i_find_heap_segment_containing_object
}

{
guilegc
Memcheck:Value4
fun:scm_markcdr
}

{
	guilegc
	Memcheck:Value4
	fun:scm_mark_locations	
}

{
	guilegc4327
   Memcheck:Cond
   obj:/usr/lib/libguile.so.12.3.0
   fun:scm_mark_locations
   fun:scm_threads_mark_stacks
   fun:scm_igc
}

{
	guilegc
	Memcheck:Cond
	fun:scm_mark_locations	
}

{
    guilegc
	Memcheck:Cond
    fun:scm_gc_mark
}


{
    guilegc
	Memcheck:Cond
    fun:scm_i_sweep_card
}

{
    guilegc
	Memcheck:Cond
    fun:scm_mark_weak_vector_spines
}


{
    guilegc
	Memcheck:Cond
    fun:scm_gc_mark_dependencies
}

{
guilegc
Memcheck:Cond
fun:scm_scan_weak_vectors
}

**


-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen



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


  reply	other threads:[~2007-01-23 22:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 15:24 Eval options macro: backward compatibility? Han-Wen Nienhuys
2007-01-20 14:35 ` Ludovic Courtès
2007-01-22 14:18   ` Han-Wen Nienhuys
2007-01-22 20:48     ` Kevin Ryde
2007-01-23  0:51       ` deprecated features Han-Wen Nienhuys
2007-01-23  1:03         ` Kevin Ryde
2007-01-23  1:20           ` Han-Wen Nienhuys
2007-01-23 14:50             ` Bruce Korb
2007-01-23 22:45               ` Han-Wen Nienhuys [this message]
2007-01-23 23:20                 ` Bruce Korb
2007-01-24  0:44                   ` Han-Wen Nienhuys
2007-01-24  0:10                     ` Bruce Korb
2007-01-23 23:10               ` Han-Wen Nienhuys
2007-01-23 23:35                 ` Bruce Korb
2007-01-24  0:38                   ` Han-Wen Nienhuys
2007-01-24 22:44             ` Kevin Ryde
2007-01-22 15:28   ` Eval options macro: backward compatibility? Han-Wen Nienhuys
2007-01-22 20:50   ` Kevin Ryde
2007-01-24 21:05 ` Kevin Ryde

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=45B68FFA.8070408@xs4all.nl \
    --to=hanwen@xs4all.nl \
    /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).