|
From: Josef W. <Jos...@gm...> - 2008-07-01 17:01:51
|
On Tuesday 01 July 2008, Bart Van Assche wrote: > On Tue, Jul 1, 2008 at 4:22 PM, Josef Weidendorfer > <Jos...@gm...> wrote: > > However, recently I asked Julian if he is fine with a short chapter about KCachegrind, > > and he agreed that this could be useful. > > The reason that I suggested to add some info about the way KCachegrind Ah, I thought the question was how to embed images into the manual, for your own tool ;-) > presents profiling data is that as far as I know this is a unique > feature. Yes, treemaps are not used often. But they are not really easy to understand without some explanation. A 1-dimensional split-up of cost probably would be enough in most cases and should be totally self-explaining. However, I agree that KCachegrind proved to be quite a good experimental prototype. > I do not know of any other profiler GUI that is as good as > KCachegrind. I consider Callgrind + KCachegrind as a strong > combination, but currently this is not emphasized in the callgrind > manual. This is true. Josef > > Bart. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |