|
From: Ashley P. <as...@qu...> - 2007-04-05 10:08:42
|
On Wed, 2007-04-04 at 23:45 -0400, Vince Weaver wrote: > > This is something I'd be interested in, if ever I get time to write a > > tool I'd like to be able to look at allocated blocks (as returned by > > malloc) and view the read/write ratio for each one, kind of like massif > > but adding a "usage rate" weighting to the graph. > > I've posted the code for my other two valgrind plugins > (all three can be found here > http://www.csl.cornell.edu/~vince/software.html > feel free to link to them from the valgrind pages) > > My cachetool plugin writes out a memory trace that has in it > info for ever load/store (for data cache simulation), every > basic block entered (for instruction cache simulation), > and every memory allocation/free (because we were tracking heap > object usage). This sounds very promising, I wouldn't want all the data it can provide but it would seem it does everything I want. > I've posted the code to the aforementioned website if you want to look at > it. I haven't tested it for a while. The trace files generated can be > quite large, so usually I'd write the output to a named pipe (mkfifo) and > then have the analysis tool run at the same time reading from it. I'd anticipated it being quite large, I'll pipe in directly into a external process. Ashley, |