From: Eric Hodel <drbrain@...7.net>
Date: 2007-10-02T05:32:44+09:00
Subject: Re: gc.c -- possible logic error?

On Oct 1, 2007, at 10:54 , Hugh Sasse wrote:
> On Tue, 2 Oct 2007, Tanaka Akira wrote:
>> The image generated by valgrind:
>> http://www.a-k-r.org/tmp/ostruct.png
>
> That's rather nice :-).  Can you get it to plot that with the heap
> at the bottom of the display?  I'm finding it hard to see if the
> heap decreases at all at the end.  It certainly does increase during
> the early stages, so it is not as if everything has been allocated
> to one chunk.  But when GC.start should make things go away, they
> don't really seem to disappear.
>
> I've seen no evidence that Ryan Davis's memory analyser:
>
> http://blog.zenspider.com/archives/2006/08/ruby_memory_vis.html
>
> ever got released, and the picture looks like a Mac gui, so I
> don't think I could use that anyway.

The mem_inspect gem is a similar tool that outputs a PNG.  It needs a  
patch to gc.c which is included.

--
Poor workers blame their tools. Good workers build better tools. The
best workers get their tools to do the work for them. -- Syndicate Wars