Re: [Valgrind-developers] Problems with Calltree using VG CVS

[Jeremy F. <je...@go...>]

On Fri, 2004-03-05 at 18:22, Josef Weidendorfer wrote:
> Hi,
> 
> I just tried Calltree to get working with Valgrind CVS.
> The version can be found at
> 	http://kcachegrind.sourceforge.net/calltree-0.9.7.tar.gz
> 
> It is almost working fine  with using "--pointercheck=no", but for large 
> programs I get the follow error when the valgrind process grows over 160M in 
> size:

Yes, the heap size for Valgrind is set to a relatively small value.  The
idea is that if a tool needs to allocate large chunks of memory, it
could use the shadow memory pool.  For most tools, this is sized by a
well-understood ratio to the client memory size - but for calltree this
doesn't necessarily make a lot of sense.

We could increase the Valgrind heap size pretty easily, but it eats into
the available client address space.  

How does Calltree use memory?  What does it allocate?

	J