https://bugs.kde.org/show_bug.cgi?id=406578
--- Comment #1 from Nick Nethercote <n.netherc...@gmail.com> ---
Valgrind 3.15 just came out and it completely overhauled DHAT. The new version
is much better.
The output is now in a tree. The root node of the tree covers the entire
program, and looks like this:
> AP 1/1 (25 children) {
> Total: 1,355,253,987 bytes (100%, 67,454.81/Minstr) in 5,943,417 blocks
> (100%, 295.82/Minstr), avg size 228.03 bytes, avg lifetime 3,134,692,250.67
> instrs (15.6% of program duration)
> At t-gmax: 423,930,307 bytes (100%) in 1,575,682 blocks (100%), avg size
> 269.05 bytes
> At t-end: 258,002 bytes (100%) in 2,129 blocks (100%), avg size 121.18
> bytes
> Reads: 5,478,606,988 bytes (100%, 272,685.7/Minstr), 4.04/byte
> Writes: 2,040,294,800 bytes (100%, 101,551.22/Minstr), 1.51/byte
> Allocated at {
> #0: [root]
> }
> }
I'm not sure I understand exactly what you're asking for, but:
- "how many times was an allocator accessed" might be the "5,943,417 blocks"
part
- "What is the read count of any width at any offset across all of blocks"
might be the "Reads: 5,478,606,988 bytes" part, though that's a byte count
rather than a read count.
Does that help?
--
You are receiving this mail because:
You are watching all bug changes.
