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

Re: git blame with valgrind massif

From
Pierre Habouzit <madcoder@debian.org>
Date
Dec 11, 2007, 21:20 UTC
Message-ID
<20071211212052.GC29110@artemis.madism.org>
In-Reply-To
<9e4733910712111257h20a4a916gd4747e816e4706ff@mail.gmail.com>
On Tue, Dec 11, 2007 at 08:57:24PM +0000, Jon Smirl wrote:
Show 5 quoted lines
> 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.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Previous: Jon SmirlNext: Jon Smirl
Message 2 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.