git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git blame with valgrind massif

From
ARAndré Goddard Rosa <andre.goddard@gmail.com>
Date
Dec 12, 2007, 00:50 UTC
Message-ID
<b8bf37780712111650i1b291cbaneea5efd16b92cb8b@mail.gmail.com>
In-Reply-To
<9e4733910712111345i23d86a85jfedb4f37f20a5b0@mail.gmail.com>
On Dec 11, 2007 7:45 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
Show 7 quoted lines
> 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
Previous: Jon SmirlNext: Linus Torvalds
Message 4 of 6 in “git blame with valgrind massif”
  1. Jon SmirlDec 11, 2007
  2. Pierre HabouzitDec 11, 2007
  3. Jon SmirlDec 11, 2007
  4. André Goddard RosaDec 12, 2007
  5. Linus TorvaldsDec 11, 2007
  6. Pierre HabouzitDec 11, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.