From: Joel VanderWerf <vjoel@...>
Date: 2002-12-03T07:50:12+09:00
Subject: Re: Valgrind

Paul Brannan wrote:
> On Mon, Dec 02, 2002 at 03:32:10AM +0900, Mathieu Bouchard wrote:
> 
>>Guy Decoux wrote:
>>
>>>valgrind is not the best tool for this.
>>
>>Then what are similar tools that are more appropriate than Valgrind for
>>debugging Ruby extensions?
> 
> 
> http://redshift.sourceforge.net/debugging-GC/
> [ruby-talk:53835]

Note that this doesn't track down memory leaks in the sense of malloc-ed 
data that are not reachable from globals, stack, etc. Rather it tells 
you *how* a reachable object is reachable.

Also, the patches are for 1.6.7 and 1.7.2. I don't what has to be done 
(if anything) for it to work with 1.7.3.