https://bugs.kde.org/show_bug.cgi?id=371916
--- Comment #9 from Ivo Raisr <iv...@ivosh.net> ---
As for the documentation, the concept is explained very well. Thank you for
this!
I found just few typos:
<para> When set to <varname>none</varname>, no memory execution
- tree is be produced.</para>
+ tree is produced.</para>
<para> When set to <varname>allocs</varname>, the memory execution
- tree gives the current number of allocated bytes and current number of
+ tree gives the current number of allocated bytes and the current number
of
allocated blocks. </para>
- bytes and blocks, the total number of freed bypes and
+ bytes and blocks, the total number of freed bytes and
- an heap usage xtree graphical representation produced by
+ a heap usage xtree graphical representation produced by
- <para><option>curB</option> current number of bytes allocated. The
+ <para><option>curB</option> current number of Bytes allocated. The
- <para><option>curBk</option> current number of blocks allocated,
+ <para><option>curBk</option> current number of Blocks allocated,
- <para>An xtree file in a Callgrind Format contains a single callgraph,
+ <para>An xtree file in the Callgrind Format contains a single callgraph,
- <para>An xtree file in a Massif Format contains one detailed tree
+ <para>An xtree file in the Massif Format contains one detailed tree
- visualiser are more versatile that the Massif Format
+ visualisers are more versatile than the Massif Format
I also wonder if you can add a paragraph or two describing how to apply xtree
analysis when profiling large programs, if possible?
--
You are receiving this mail because:
You are watching all bug changes.
