git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "André Goddard Rosa" <andre.goddard@gmail.com>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: "Pierre Habouzit" <madcoder@debian.org>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git blame with valgrind massif
Date: Tue, 11 Dec 2007 22:50:53 -0200	[thread overview]
Message-ID: <b8bf37780712111650i1b291cbaneea5efd16b92cb8b@mail.gmail.com> (raw)
In-Reply-To: <9e4733910712111345i23d86a85jfedb4f37f20a5b0@mail.gmail.com>

On Dec 11, 2007 7:45 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
> On 12/11/07, Pierre Habouzit <madcoder@debian.org> 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?

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

  reply	other threads:[~2007-12-12  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 20:57 git blame with valgrind massif Jon Smirl
2007-12-11 21:20 ` Pierre Habouzit
2007-12-11 21:45   ` Jon Smirl
2007-12-12  0:50     ` André Goddard Rosa [this message]
2007-12-11 21:22 ` Linus Torvalds
2007-12-11 21:27   ` Pierre Habouzit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b8bf37780712111650i1b291cbaneea5efd16b92cb8b@mail.gmail.com \
    --to=andre.goddard@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jonsmirl@gmail.com \
    --cc=madcoder@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).