Re: git blame with valgrind massif

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/11/07, Pierre Habouzit <madcoder@xxxxxxxxxx> wrote:
> On Tue, Dec 11, 2007 at 08:57:24PM +0000, Jon Smirl wrote:
> > I ran:
> >  valgrind --tool=massif --heap=yes git blame gcc/ChangeLog
> > it used about 2.25GB
> >
> > How do you interpret the massif output?
>
>   would you mind putting the postscript it generated somewhere too ?
> it's usually pretty informative, because the amount of data allocated is
> not all, its liveness is an important information too.

It was very boring. A diagonal line from 0 to 2GB.

>
> --
> ·O·  Pierre Habouzit
> ··O                                                madcoder@xxxxxxxxxx
> OOO                                                http://www.madism.org
>
>


-- 
Jon Smirl
jonsmirl@xxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux