I think that's it, exactly. A lot of information, as expected, but I can write something to parse it and find what I actually need. That "memview" also looks useful but probably would have required some changes. This does exactly what I need. Thanks a lot, this is going to save me a lot of time.
On Thu, Oct 30, 2014 at 1:44 PM, Eliot Moss <m...@cs.umass.edu> wrote: > You can get a trace of memory accesses from lackey. You would need to > process it down a bit if all you want is counts and if you want to sort it > by location, but it would be reasonably easy to do that. > Eliot Moss > > On October 30, 2014 1:36:14 PM EDT, David Goldsmith <wiz...@houseoffire.ca> > wrote: >> >> Hi, >> is there something in the Valgrind tools that will give me some kind >> of map of all memory accesses? I have a chunk of memory and I want to >> know what parts of it are read from, which are written to, and which >> are never touched at all. Cachegrind seems to almost do this, it >> takes counts of when memory read/write occurs but in addition to the >> count I also need to know the exact location that it is accessing. >> Does this functionality exist somewhere in the toolset and I just >> can't find it? >> Thanks! >> >> ________________________________ >> >> ________________________________ >> >> Valgrind-users mailing list >> Valgrind-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
