Re: git blame with valgrind massif

On Dec 11, 2007 7:45 PM, Jon Smirl [off-list ref] wrote:

On 12/11/07, Pierre Habouzit [off-list ref] wrote:

quoted

On Tue, Dec 11, 2007 at 08:57:24PM +0000, Jon Smirl wrote:

quoted

I ran:
 valgrind --tool=massif --heap=yes git blame gcc/ChangeLog
it used about 2.25GB

How do you interpret the massif output?

A bit unrelated, but there's a new valgrind release:
http://www.valgrind.org/docs/manual/dist.news.html

"The main excitement in 3.3.0 is new and improved tools.  Helgrind
works again, Massif has been completely overhauled and much improved,
Cachegrind now does branch-misprediction profiling, and a new category
of experimental tools has been created, containing two new tools:
Omega and DRD.  There are many other smaller improvements."

Best regards,
-- 
[]s,
André Goddard